Re: Buster => Bullseye: packages kept back

[Jeffrey Walton <noloader@gmail.com>]

On Sun, Mar 26, 2023 at 5:16 AM Jesper Dybdal <jd-debian-user@dybdal.dk> wrote:
>
> Yesterday, I upgraded Buster => Bullseye.
>
> This morning, I got a mail from unattended-upgrades, which said:
>
> > Packages with upgradable origin but kept back:
> >   Debian stable:
> >    guile-2.2-libs w3m
>
> and
> > Package guile-2.2-libs is kept back because a related package is kept back or due to local apt_preferences(5).
> > Package w3m is kept back because a related package is kept back or due to local apt_preferences(5).
> What does this mean?  I have what I believe to be a clean install, I
> have never used apt_preferences, and until now, I had never heard of
> guile or w3m.  And I don't quite understand why I have them installed at
> all.  My sources.list contains only bullseye and bullseye-backports.
>
> What do I do?
>
> apt list says:
> > guile-2.2-libs/stable 2.2.7+1-6 amd64 [upgradable from: 2.2.4+1-2+deb10u1]
> > guile-2.2-libs/now 2.2.4+1-2+deb10u1 amd64 [installed,upgradable to:
> > 2.2.7+1-6]
> >
> > w3m/stable 0.5.3+git20210102-6 amd64 [upgradable from: 0.5.3-37]
> > w3m/now 0.5.3-37 amd64 [installed,upgradable to: 0.5.3+git20210102-6]

I would install aptitude, and then run `aptitude safe-upgrade`.
Aptitude's solver can usually determine the upgrade path that avoids
breaking the machine.

Jeff