20.04.4 to 22.04.1 upgrade: dovecot-core, libdvd-pkg, VirtualBox, amdgpu

[Liam Proven]

On Mon, 22 Aug 2022 at 04:45, Andrew J. Caines <A.J.Caines at halplant.com> wrote:
>
> Fellow present and future upgraders,
>
> My primary workstation has been upgraded to a newer LTS release before.
> It has LVM,

Uhoh.

> LUKS encryption,

Double uhoh.

> swap volume, ext2 on /boot, ext4 on /,
> btrfs,

Btrfs *and* ext4? Why? Which is on which?

> VirtualBox VMs, GNOME desktop, amdgpu driver,

Nothing terribly relevant there...

> packages,

What packages?

> Snaps and
> Flatpaks and runs some network application services.

*Gulp*

> The upgrade was run from Software Updater completed, but with errors.
> This is a terse summary with some observations.

OK. How much free space did you have before you started? How did you
check? (Btrfs lies about free space. It's one of many reasons I won't
use it.)


> I re-ran Update Manager to see the result, which was just some old
> kernels ready to autoremove, but then

After `dpkg-reconfigure -a` the normal next step is

sudo apt-install -f

> Dealing with updated config files wasn't an issue since I knew what to
> keep and replace, but with the recent default changes in OpenSSH and my
> modified sshd_config, I tried a three-way merge, which failed, so I
> installed the package version, then made my modifications later.

Ouch.

> Since the install left a lot of packages for autoremoval which I was not
> yet ready to remove after the install errors, I removed the older kernel
> packages.
>
> ----8<----
> $ uname -r
> 5.4.0-124-generic
> ajc at hal11000:~$ ls -lt /boot/*-5.4.0-???-generic
> -rw-r--r-- 1 root root 93031002 Aug 19 19:58
> /boot/initrd.img-5.4.0-124-generic

Hang on. You weren't on the HWE stack already? Any particular reason why not?

With such an extraordinarily complex setup, I'd be keeping it as
current as possible at all times, but I guess maybe that's just me.

5.4 is the wrong kernel for 22.04. It uses 5.15. You still have the
original 20.04 kernel.

> I re-ran Update Manager.

Wrong tool. `apt install -f` is needed to try to clean up the package
database. You should have done this before proceeding. I'm surprised
anything else worked TBH, unless you did it and didn't mention it?

> After re-enabling the repo which had been updated to jammy, updating
> virtualbox-6.1 and fixing the repo to ignore i386 (again) with

You know, VirtualBox is in the repos and you don't really need an
external version unless there's something in it you require.

The KISS principle always applies.

> Trying to install the latest AMDGPU driver[2] for jammy after removing
> the installed one for focal and cleaning out the old repos fails to find
> various packages depending on the install type, but adding a repo for
> "main" fixed the missing packages errors. I'm sure I missed something
> for doing this the easy and right way.

This is a bit worrying...

> While the same may apply to Snaps and Flatpaks, I did not change the
> three Snap applications in ~/snap/ or any Flatpaks since they don't
> change with the Ubuntu update, however a couple of Flatpaks launched
> "fresh", requiring authentication for the first run.

When you update, do you update those systems to?

Me personally, every day, I run this sequence:

sudo -s
(up-arrow to recall previous command)
apt update ; apt full-upgrade -y ; apt autoremove -y ; apt purge ; apt
clean ; snap refresh ; flatpak update



-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lproven at cix.co.uk ~ gMail/gTalk/FB: lproven at gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053