Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #195210 > unrolled thread

messed up release in apt

Back to article view | Back to linux.debian.user

Contents

  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

#195210 — messed up release in apt

hello,
I mistakenly added an etc/apt/sources.list line for "jessie"(backports)
instead of "stretch", which is my current release. I proceded to update
apt and installed Wine (along with many packages, some i386) from the
jessie-backports source (i.e. apt install wine/jessie-backports).
Please tell me how I can locate all wrongly installed packages and
remove them, and install correct packages from stretch-backports,
thank you,

[toc] | [next] | [standalone]

#195215

On Mon 30 Apr 2018 at 11:49:33 -0500, Anil Duggirala wrote:

> hello,
> I mistakenly added an etc/apt/sources.list line for "jessie"(backports)
> instead of "stretch", which is my current release. I proceded to update
> apt and installed Wine (along with many packages, some i386) from the
> jessie-backports source (i.e. apt install wine/jessie-backports).
> Please tell me how I can locate all wrongly installed packages and
> remove them, and install correct packages from stretch-backports,
> thank you,

Take a look at apt's log in /var/log.

Or let apt sort it out with the correct line in sources.list and then
update and upgrade.

Or, both.

-- 
Brian.
 

[toc] | [prev] | [next] | [standalone]

#195220

On 30-04-18, Brian wrote:
> On Mon 30 Apr 2018 at 11:49:33 -0500, Anil Duggirala wrote:
> 
> > hello,
> > I mistakenly added an etc/apt/sources.list line for "jessie"(backports)
> > instead of "stretch", which is my current release. I proceded to update
> > apt and installed Wine (along with many packages, some i386) from the
> > jessie-backports source (i.e. apt install wine/jessie-backports).
> > Please tell me how I can locate all wrongly installed packages and
> > remove them, and install correct packages from stretch-backports,
> > thank you,
> 
> Take a look at apt's log in /var/log.
> 
> Or let apt sort it out with the correct line in sources.list and then
> update and upgrade.
> 
> Or, both.
> 
> -- 
> Brian.
>  
> 

I would first use old sources.list to purge wine and follow it up with
autoremove. But after that new, this time intended and correct,
sources.list with apt-get should solve problem.

[toc] | [prev] | [next] | [standalone]

#195227

> I would first use old sources.list to purge wine and follow it up
> with
> autoremove. But after that new, this time intended and correct,
> sources.list with apt-get should solve problem.
> 

When you say "old" do you mean the sources.list without the jessie
backports entry? Could you explain to me why exactly you would do that,
thanks a lot for your help

[toc] | [prev] | [next] | [standalone]

#195236

On 30-04-18, Anil Duggirala wrote:
> > I would first use old sources.list to purge wine and follow it up
> > with
> > autoremove. But after that new, this time intended and correct,
> > sources.list with apt-get should solve problem.
> > 
> 
> When you say "old" do you mean the sources.list without the jessie
> backports entry? Could you explain to me why exactly you would do that,
> thanks a lot for your help
> 

By old, I was referring to sources.list with jessie backports. I wold do
that to make sure that apt will clean up all dependencies for Wine in
jessie backports. It is probably not needed and it is more than likely
overkill, but I'm always bit of paranoid when it comes to mixing up
things in sources.list, specially when backports are involved. Simply
changing your sources.list to correct backports and then doing update
and upgrade with apt should get you version of Wine with dependencies
for stretch backports. 

Sorry for possible confusion and for not explaining it bit better in
first place.

[toc] | [prev] | [next] | [standalone]

#195242

> By old, I was referring to sources.list with jessie backports. I wold
> do
> that to make sure that apt will clean up all dependencies for Wine in
> jessie backports. 

I thought that was what you meant, I did as you instructed. Just trying
to get rid of this "key" error now.
thanks a lot,

[toc] | [prev] | [next] | [standalone]

#195221

On 2018-04-30, Anil Duggirala <anilduggirala@fastmail.fm> wrote:
> hello,
> I mistakenly added an etc/apt/sources.list line for "jessie"(backports)
> instead of "stretch", which is my current release. I proceded to update
> apt and installed Wine (along with many packages, some i386) from the
> jessie-backports source (i.e. apt install wine/jessie-backports).
> Please tell me how I can locate all wrongly installed packages and
> remove them, and install correct packages from stretch-backports,
> thank you,
>
>

The Debian English-language backports wiki FAQ suggests (to find
all backported packages on a given machine):

https://backports.debian.org/FAQ/

 dpkg -l  |awk '/^ii/ && $3 ~ /bpo[7-9]/ {print $2}'
 (works here--outputs the package name without version)

 aptitude search '?narrow(?version(CURRENT),?origin(Debian Backports))'-F '%100p'
 (produces no output here though I have one backported package).

The French (ah, the French) backports FAQ suggests:

https://wiki.debian.org/fr/Backports

 dpkg-query -W | grep ~bpo
 (works here--outputs package + version)

Then there is the '/var/log/apt/history.log' also, which might be of
great utility in this affair.

-- 
"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

[toc] | [prev] | [next] | [standalone]

#195231

> > The Debian English-language backports wiki FAQ suggests (to find
> all backported packages on a given machine):
> 
> https://backports.debian.org/FAQ/
> 

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!

[toc] | [prev] | [next] | [standalone]

#195237

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

[toc] | [prev] | [next] | [standalone]

#195243

> 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.

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

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

[toc] | [prev] | [next] | [standalone]

#195244

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...

-- 

[toc] | [prev] | [next] | [standalone]

#195245

On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala 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.
> 
> > after removing 
> > 
> >  '/etc/apt/trusted.gpg' 
> > 
> When you say removing you mean :
> rm /etc/apt/trusted.gpg ?
> 
> I appreciate any other alternative procedure to correct this,
> thanks,

I don't know if this rather long thread would help. It does appear
that /etc/apt/trusted.gpg is no longer used, in favour of
/etc/apt/trusted.gpg.d/ but if the former exists, it can cause
problems. There's a new user on stretch called _apt but I don't
know its function.

https://lists.debian.org/debian-user/2017/07/msg00289.html

BTW when someone writes "remove file foo", it's generally safer
to interpret this as "mv -i foo some-safe-hidden-place" rather
than destroying its contents altogether. The same goes for
directories, move them rather than deleting them.

A lot of configuration files have rather strict naming requirements
which makes them very easy to hide.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#195247

On Tue 01 May 2018 at 09:18:56 -0500, David Wright wrote:

> On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala 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.
> > 
> > > after removing 
> > > 
> > >  '/etc/apt/trusted.gpg' 
> > > 
> > When you say removing you mean :
> > rm /etc/apt/trusted.gpg ?
> > 
> > I appreciate any other alternative procedure to correct this,
> > thanks,
> 
> I don't know if this rather long thread would help. It does appear
> that /etc/apt/trusted.gpg is no longer used, in favour of
> /etc/apt/trusted.gpg.d/ but if the former exists, it can cause
> problems. There's a new user on stretch called _apt but I don't
> know its function.

A security enhancement. _apt is an unprivileged user, allowing
sandboxed downloading. The user exists to protect against bugs
in the http protocol handler, ssl libraries, compressors, etc.
It also protects against permission issues elsewhere.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#195309

I have removed the /etc/apt/trusted.gpg and that removed the error from apt update.
I will try now adding correct stretch-backports and installing the packages I  require,
thanks a lot, 

On Tue, May 1, 2018, at 12:29 PM, Brian wrote:
> On Tue 01 May 2018 at 09:18:56 -0500, David Wright wrote:
> 
> > On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala 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.
> > > 
> > > > after removing 
> > > > 
> > > >  '/etc/apt/trusted.gpg' 
> > > > 
> > > When you say removing you mean :
> > > rm /etc/apt/trusted.gpg ?
> > > 
> > > I appreciate any other alternative procedure to correct this,
> > > thanks,
> > 
> > I don't know if this rather long thread would help. It does appear
> > that /etc/apt/trusted.gpg is no longer used, in favour of
> > /etc/apt/trusted.gpg.d/ but if the former exists, it can cause
> > problems. There's a new user on stretch called _apt but I don't
> > know its function.
> 
> A security enhancement. _apt is an unprivileged user, allowing
> sandboxed downloading. The user exists to protect against bugs
> in the http protocol handler, ssl libraries, compressors, etc.
> It also protects against permission issues elsewhere.
> 
> -- 
> Brian.
> 

[toc] | [prev] | [next] | [standalone]

#195246

On 05/01/2018 06:11 AM, Anil Duggirala 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.
> 
>> after removing
>>
>>   '/etc/apt/trusted.gpg'
>>
> When you say removing you mean :
> rm /etc/apt/trusted.gpg ?
> 
> I appreciate any other alternative procedure to correct this,
> thanks,


If you have a desktop and Synaptic installed you can do all the things 
you want to do in Synaptic, like force a different version and 
reinstalling the keyring or installing distro-info.

Cheers,
-- 
Jimmy Johnson

Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#195228

On Mon, 30 Apr 2018 11:49:33 -0500 Anil Duggirala said:

> Please tell me how I can locate all wrongly installed packages and
> remove them, and install correct packages from stretch-backports,

Hello Anil,

I think while Curt's dpkg/awk solution is elegant, /var/log/apt/history.log* is
more deterministic.

I would remove the jessie-backports line from sources.list, apt-get update,
then remove every package previous upgrade installed, force-reinstall (from
stretch repos) every package previous upgrade upgraded, install every package
(from stretch) previous upgrade removed, all in a single long "apt-get install"
line.

PS: It is possible to remove a package via apt-get "install" command with a
hyphen prepended to the package name.

Regards.
-- 
Abdullah Ramazanoglu

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web