That fails when we use tagged snapshots, since such packages doesn't
exist which makes apt-get bail out.

I'd rather remove the affected apt-get call, but I wonder if that
could have consequences, so I'll open a ticket about what to do
instead.

While preparing 3.12~rc1 I was failing to tag the snapshots using
apt-tag-snapshot, getting the error "[t]wo [source] lines describing
'linux' [...]". Indeed, we were mixing linux-{headers,image}* version
4.19.13-1 and linux-{kbuild,source}-4.19 version 4.19.16-1, and our
tagged snapshot design doesn't support this.

I'm about to prepare Tails 3.12~rc1, and our release notes depends on
our changelog to use that exact version.

Merge remote-tracking branch 'origin/bugfix/16365-update-network-manager' into testing (Fix-committed: #16365)

My build of devel/testing + #16365 just got OOM killed. I'm about to
prepare Tails 3.12~rc1 and do not want to fight with these kind of
issues.

On Tails 3.11, hostname(1) returns… "localhost.localdomain".
I assume that's been the case since #13574 and #15322.
So we were not testing whether "amnesia" leaks in DHCP requests anymore.

Let's check for both "amnesia" and whatever hostname(1) returns.

It's too late to deal with this now.

These were still missing on my Sid system.