On Mon, May 24, 2021 at 08:44:55PM +0200, Paul Gevers wrote: > Hi, > > On 23-05-2021 08:55, Bill Allombert wrote: > > On Sat, May 22, 2021 at 11:01:54PM +0200, Paul Gevers wrote: > >> Hi Bill, > >> > >> On 22-05-2021 21:42, Bill Allombert wrote: > >>> Do you have a list of packages whose upgrade triggers this issue ? > >> > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=988003;filename=Samantha_upgrade_logs.tar.gz;msg=5 > >> has a dpkg-get-selection file with the list of installed packages. > > > > Unfortunately, I do not have enough diskspace try to reproduce it > > right now. > > > > Generally to find out why a package foo is not upgraded, one do > > apt-get install guile-2.2-libs > > and see what apt reports. > > I have used the dpkg-get-selections as input in a stable lxc, changed > the distribution to bullseye, done an $(apt upgrade --without-new-pkgs) > and then tried to run $(apt-get install guile-2.2-libs). Please find the > output below. I *guess* the suspecting things are the pieces which "will > be removed". Do we see anything suspicious? > > I'll keep the container for some days (if I don't need the disk space).
Thanks, this useful. Could you also do it after the first 'apt-get full-upgrade' to compare ? We should get a much smaller set of packages. Cheers, Bill
