Re: Buster => Bullseye: packages kept back
On Sun, 26 Mar 2023 Jesper Dybdal wrote:
Thanks a lot for the responses.
It is a confusing mystery!
I'm still in doubt as to what to do.
I notice that according to your posted output from the commands,
apt-get -Vs remove {w3m,guile-2.2-libs}
that both packages now appear to be up-to-date, relative to the
versions current in bullseye:
https://www.dybdal.dk/bullseye/apt-get-Vs-remove-w3m.txt
[...]
The following packages will be REMOVED:
w3m (0.5.3+git20210102-6)
https://www.dybdal.dk/bullseye/apt-get-Vs-remove-guile.txt
[...]
The following packages will be REMOVED:
guile-2.2-libs (2.2.7+1-6)
libmailutils7 (1:3.10-3+b1)
mailutils (1:3.10-3+b1)
One thing I forgot to mention yesterday, but which I now think may
be correlated with this problem, is that yesterday's upgrade
mysteriously removed roundcube. I have no idea why, and I want it
back, but that is not particularly urgent. I wonder if roundcube
could have some dependencies that influence the other problem.
Even on my good days, your guess is probably better than mine. And in
my present state of confusion, I will decline to speculate. :D
I have saved the responses to some of your suggested commands; they
may not be interesting,
They were.
but just in case, they are available at
https://www.dybdal.dk/bullseye
with links in the text below.
Yes, I was curious. Thank you.
On 2023-03-26 13:17, davidson wrote:
On Sun, 26 Mar 2023 Jesper Dybdal wrote:
[trimmed]
$ apt-mark showauto | grep -xE 'guile-2.2-libs|w3m'
By the way, I learned today that the same output can be had more
simply with
$ apt-mark showauto guile-2.2-libs w3m
[trimmed]
My sources.list contains only bullseye and bullseye-backports.
Today it does.
But the day before yesterday, I gather it was Buster's Last Stand.
Indeed. And at that time, sources.list contained just buster and
buster-backports.
By the way, does your sources.list really have no line for security
updates? Nothing like this one?
deb http://security.debian.org/debian-security bullseye-security main non-free
[trimmed]
FIRST OPTION:
[trimmed]
# aptitude search '~o'
# aptitude purge '~o'
I guess you could try that search command above, first. And then if
you don't care about purging the obsolete packages it lists, then I
guess you could purge them, to see if that permits you to upgrade
these two packages that you never knew you had installed, and never
explicitly asked for.
The search command gives a list of 108 packages, which I'm somewhat
reluctant to purge.
Output in https://www.dybdal.dk/bullseye/aptitude-search-obsolete.txt
I do not use aptitude at all, and therefore know nothing about it. So
do not construe the next bit as advice.
In the absence of a particular reason to keep around a package which
won't receive updates (security or otherwise) during a system
release's lifetime, I am personally inclined to purge it, one way or
another. (Not with aptitude, though, because I don't know the first
thing about how to keep it from doing things I don't want done.)
Sometimes there are reasons to keep them, of course.
And I hear that some people don't even need reasons, if you can
believe this. They just do whatever they want!
SECOND OPTION:
[trim]
$ apt-get -Vs remove w3m
That gives a list of 129 packages that "were automatically installed
and are no longer required" but as I understand it, it will remove
only w3m, not those 129 packages.
True. APT is just keeping you informed.
Output in https://www.dybdal.dk/bullseye/apt-get-Vs-remove-w3m.txt
Comparing the autoremoval list in the output above to your list of
obsolete packages
https://www.dybdal.dk/bullseye/aptitude-search-obsolete.txt
it looks like among those 129 packages, that
# apt-get autoremove
would remove many (about 46?) of the obsolete packages.
You can use
# apt-mark manual favorite-package1 favorite-package2 ...
to keep favorite-packages from being autoremoved.
and
$ apt-get -Vs guile-2.2-libs
I have resisted the compulsion to correct my own typo in the above
command.
That gives first a list of 134 packages, and then:
It baffles me that the number of packages suggested for autoremoval is
different, between guile-2.2-libs and w3m.
The following packages will be REMOVED:
guile-2.2-libs (2.2.7+1-6)
libmailutils7 (1:3.10-3+b1)
mailutils (1:3.10-3+b1)
I am not quite certain that I do not use or will use mailutils.
To me, those mailutils package versions look up-to-date for bullseye
now, as does guile-2.2-libs!
[trim]
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]
(Above excerpt left untrimmed for easy comparison with more recent output.)
[trimmed discussion of mailutils]
But perhaps I will try to install the lost roundcube again first,
and see if it changes the state.
Does that sound sensible?
Sure.
Again thanks for your help,
It's been very interesting. Have a good week.
--
Hackers are free people. They are like artists. If they are in a good
mood, they get up in the morning and begin painting their pictures.
-- Vladimir Putin
Reply to: