Re: Buster to Bullseye upgrade problem
On Wed 18 Aug 2021, at 00:44, Gareth Evans <donotspam@fastmail.fm> wrote:
> Hello,
>
> I upgraded from Buster stable to Bullseye stable last night, with
> apparent success eventually, but it went less than smoothly and I would
> be grateful for any advice as to why that may have been.
>
> I followed the preparation advice at
>
> https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html
>
> and it seemed to me that there were no non-Debian packages in
> apt-forktracer output, although I'm afraid I didn't save the list.
>
> The upgrade process stopped abruptly a couple of times, once without
> any indication as to why.
>
> $ cat /etc/apt/sources.list
> deb http://deb.debian.org/debian/ bullseye main contrib non-free
> deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
> #deb http://deb.debian.org/debian bullseye-proposed-updates main
> contrib non-free
> deb http://deb.debian.org/debian-security/ bullseye-security main
> contrib non-free
> deb http://deb.debian.org/debian/ bullseye-backports main contrib
> non-free
>
>
> >From script output:
>
> # apt full-upgrade
> [...]
> Errors were encountered while processing:
> /tmp/apt-dpkg-install-2vllSE/09-gir1.2-gst-plugins-bad-1.0_1.18.4-3_amd64.deb
> <upgrade stopped, etckeeper output snipped>
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> # apt install --fix-broken
> [...]
> Setting up zfs-initramfs (2.0.3-9) ...
> Processing triggers for initramfs-tools (0.133+deb10u1) ...
> update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
>
> # apt full-upgrade
> [...]
> Processing triggers for libapache2-mod-php7.4 (7.4.21-1+deb11u1) ...
> <upgrade stopped, etckeeper output snipped>
> W: APT had planned for dpkg to do more than it reported back (8974 vs
> 9007).
> Affected packages: texlive-fonts-recommended:amd64
> texlive-lang-greek:amd64 texlive-latex-base:amd64
> texlive-latex-extra:amd64 texlive-latex-recommended:amd64
> texlive-pictures:amd64 texlive-plain-generic:amd64 texlive-science:amd64
>
> # apt full-upgrade
> [...]
>
> Apparent success...
>
> $ apt policy *gir*bad*
> gir1.2-gst-plugins-bad-1.0:
> Installed: 1.18.4-3
> Candidate: 1.18.4-3
> Version table:
> *** 1.18.4-3 500
> 500 http://deb.debian.org/debian bullseye/main amd64 Packages
> 100 /var/lib/dpkg/status
>
> $ cat /etc/debian_version
> 11.0
>
> $ uname -a
> Linux <hostname> 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03)
> x86_64 GNU/Linux
>
> Reboots without issue.
>
> Is there any way to verify an upgrade completed properly? Would there
> be obvious errors on exit if it didn't?
>
> Thanks,
> Gareth
>
>
I have been digging/experimenting a bit more and have reverted to Buster several times by rolling back zfs snapshots to retry upgrading with different approaches:
(1) Minimal system upgrade, then full-upgrade, per
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
Minimal upgrade completed without issue, but the same problems with the same solutions as in my first email appeared in the full-upgrade part of the process.
(2) Single-line sources.list:
deb http://deb.debian.org/debian/ bullseye main contrib non-free
Same approach as in (1), same problems and solutions.
(3) Minimal upgrade followed by "apt upgrade" (not full-upgrade) - this is apparently not to be recommended! (I know this is what full/dist-upgrade is for, but I thought I'd see what happened.) Fwiw...
There were no breakages in the upgrade process in this approach, but then the system dropped to initramfs on reboot due to lack of zfs modules (much building having been conspicuous by its absence). Booting into a previous kernel at this stage got to graphical login, all Bullseye themed so far, but no desktop appeared after successful login, and *Buster* shutdown screen appeared after holding power off.
So whatever way I approach it, the upgrade doesn't run smoothly at all, though it seems to succeed eventually using a combination of
[optionally...] apt upgrade --without-new-pkgs
apt full-upgrade
apt install --fix-broken
apt full-upgrade x2
As for causes...
syslog is silent on the issues
/var/log/apt/term.log shows:
--
Unpacking gir1.2-gst-plugins-bad-1.0:amd64 (1.18.4-3) ...
[1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-Un4rDW/28-gir1.2-gst-plugins-bad-1.0_1.18.4-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/girepository-1.0/GstTranscoder-1.0.typelib', which is also in package pitivi 0.999-1+b1
[1mdpkg-deb:[0m [1;31merror:[0m paste subprocess was killed by signal (Broken pipe)
--
However it gives no clue as to why the upgrade stops again later, with things for apt still to do, after the second (of three) "apt full-upgrade"s, saying merely:
--
Processing triggers for libapache2-mod-php7.4 (7.4.21-1+deb11u1) ...
Log ended: 2021-08-18 11:09:56
--
A quick google shows etckeeper causes problems at times, but nothing along these lines afaics, and at least one person appears to succeed in using it while upgrading Buster -> Bullseye
https://chris.hofstaedtler.name/blog/2021/04/bullseye-upgrade-notes.html
So afaict, I have an upgraded system:
$ cat /etc/debian_version
11.0
$ uname -a
Linux <hostname> 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
$ sudo apt update
[...]
All packages are up to date.
$ sudo apt full-upgrade
[...]
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
But I would like to understand what's going wrong with this.
If anyone has theories/suggestions for me to test I would be happy to report results, especially if it might help others. Is any of this bug report-worthy? If so, against what?
Thanks,
Gareth
Reply to: