Groups > linux.debian.user > #195237

Re: messed up release in apt

From	Curt <curty@free.fr>
Newsgroups	linux.debian.user
Subject	Re: messed up release in apt
Date	2018-05-01 10:10 +0200
Message-ID	<vKywh-8mR-3@gated-at.bofh.it> (permalink)
References	<vKkjE-6Ny-9@gated-at.bofh.it> <vKlpn-7Jv-1@gated-at.bofh.it> <vKqfn-2zv-1@gated-at.bofh.it>
Organization	Unorganized

Show all headers | View raw

On 2018-04-30, Anil Duggirala <anilduggirala@fastmail.fm> wrote:
>
> I  removed all backported packages. Then did apt-get autoremove. Then
> removed the jessie-backports line from sources.list. I appear to have
> come back to my original system. However I am now getting an error on
> apt update.
> W: http://security.debian.org/debian-security/dists/stretch/updates/InR
> elease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as
> the file is not readable by user '_apt' executing apt-key.
> W: http://ftp.us.debian.org/debian/dists/stretch-updates/InRelease: The
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
>
> Any help on that?
> thanks!
>

I'm uncertain.

If it were my machine (so that if I sank it I would be the only one to
go down with the ship), I might run:

 'apt-key update'

after removing 

 '/etc/apt/trusted.gpg' 

This gleaned from the innertubes.

Maybe someone more knowledgable will pipe up.

-- 
"Three prisoners were locked in a cell. When the largest of them finished his
food, he immediately ate the others. Too bad. An apostrophe in the right place
might have prevented a horrible crime." Joe Gunn

Thread

messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-30 19:00 +0200
  Re: messed up release in apt Brian <ad44@cityscape.co.uk> - 2018-04-30 19:50 +0200
    Re: messed up release in apt Dejan Jocic <jodejka@gmail.com> - 2018-04-30 20:00 +0200
      Re: messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-05-01 00:10 +0200
        Re: messed up release in apt Dejan Jocic <jodejka@gmail.com> - 2018-05-01 09:20 +0200
          Re: messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-05-01 15:10 +0200
  Re: messed up release in apt Curt <curty@free.fr> - 2018-04-30 20:10 +0200
    Re: messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-05-01 01:20 +0200
      Re: messed up release in apt Curt <curty@free.fr> - 2018-05-01 10:10 +0200
        Re: messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-05-01 15:20 +0200
          Re: messed up release in apt Curt <curty@free.fr> - 2018-05-01 16:10 +0200
          Re: messed up release in apt David Wright <deblis@lionunicorn.co.uk> - 2018-05-01 16:30 +0200
            Re: messed up release in apt Brian <ad44@cityscape.co.uk> - 2018-05-01 19:30 +0200
              Re: messed up release in apt Anil Duggirala <anilduggirala@fastmail.fm> - 2018-05-05 23:40 +0200
          Re: messed up release in apt Jimmy Johnson <field.engineer@gmail.com> - 2018-05-01 17:00 +0200
  Re: messed up release in apt Abdullah Ramazanoglu <ar018@yahoo.com> - 2018-05-01 00:30 +0200

csiph-web