Oops, one wrong address, re-sending. On 22-05-2021 09:52, Paul Gevers wrote: > Control: severity 988003 normal > Control: merge -1 988003 > Control: affects -1 release-notes guile-2.2 > > Hi Apt maintainers, Rob, > > On 21-05-2021 23:47, Vagrant Cascadian wrote: >> Package: upgrade-reports >> Severity: normal >> X-Debbugs-Cc: vagrant@debian.org >> >> On numerous systems I have upgraded recently, the process of: >> >> apt upgrade --without-new-pkgs >> apt full-upgrade >> >> Results in at least one package (guile-2.2-libs, zile, sometimes others) >> in an un-upgraded state. >> >> Running a second "apt full-upgrade" seems to take care of the issue. >> >> Maybe upgrading apt in-between "apt upgrade --without-new-pkgs" and "apt >> full-upgrade" would resolve the issue? > > This is the second report we receive about buster to bullseye upgrades > leaving some packages in a non-upgraded state with the recommended > upgrade procedure. Both reports involve guile-2.2-libs. Does any of you > see why that could happen? Is this something we should worry about? Do > we need to update the release notes update procedure (is apt upgrade and > apt full-upgrade not enough) or is this the fault of guile-2.2-libs or > apt? I tend to think there is probably a complex relation preventing apt > to do the rigth thing in one go, but as the upgrade happens after a > second run, apparently it's not really blocking > > Paul >
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature