Groups > linux.debian.user > #195244

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 16:10 +0200
Message-ID	<vKE8F-3KQ-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> <vKywh-8mR-3@gated-at.bofh.it> <vKDmi-3aA-5@gated-at.bofh.it>
Organization	Unorganized

Show all headers | View raw

On 2018-05-01, Anil Duggirala <anilduggirala@fastmail.fm> wrote:
>> 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'
>> 
>
> When running that command I am getting :
> Warning: 'apt-key update' is deprecated and should not be used anymore!
> Note: In your distribution this command is a no-op and can therefore be
> removed safely.

I guess I gave you some (obsolete) bad advice.

I don't know what the solution to your problem is because I don't know
what is provoking it.  

My idea was to regenerate the '/etc/apt/trusted.gpg' file; it appears
'apt-key update' is not (no longer?) a secure way of doing so, thus the
deprecation.

>> after removing 
>> 
>>  '/etc/apt/trusted.gpg' 
>> 
> When you say removing you mean :
> rm /etc/apt/trusted.gpg ?

I should have told you to back it up first.

> I appreciate any other alternative procedure to correct this,
> thanks,

I can only think of reinstalling the 'debian-archive-keyring'. Of course
if apt is inoperable you'll have to download the Stretch package and
'dpkg -i'... 

But as I've already put my foot in my mouth...

--

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