noble staging failure in CI for test_all_packages_updated

[legoktm]

Description

assert "0 upgraded, 0 newly installed, 0 to remove" in c.stdout fails for:

NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following upgrades have been deferred due to phasing:
  libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 systemd
  systemd-dev systemd-resolved systemd-sysv systemd-timesyncd udev
The following packages will be upgraded:
  libdrm-common libdrm2
2 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
Inst libdrm-common [2.4.120-2build1] (2.4.122-1~ubuntu0.24.04.1 Ubuntu:24.04/noble-updates [all])
Inst libdrm2 [2.4.120-2build1] (2.4.122-1~ubuntu0.24.04.1 Ubuntu:24.04/noble-updates [amd64])
Conf libdrm-common (2.4.122-1~ubuntu0.24.04.1 Ubuntu:24.04/noble-updates [all])
Conf libdrm2 (2.4.122-1~ubuntu0.24.04.1 Ubuntu:24.04/noble-updates [amd64])

https://github.com/freedomofpress/securedrop/actions/runs/13065618335/job/36457392613

I have not looked to see why libdrm wasn't already upgraded.

[legoktm]

Based on reading https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-19/+bug/2083020, libdrm was upgraded as a dependency of mesa. mesa is being phased, but I don't see why that would affect the installation of libdrm...

[legoktm]

We can confirm libdrm is not being phased by looking at:

$ apt show libgbm1
Package: libgbm1
Version: 24.2.8-1ubuntu1~24.04.1
Priority: optional
Section: libs
Source: mesa
Origin: Ubuntu
Phased-Update-Percentage: 40
...

But apt show libdrm2 contains no "Phased-Update-Percentage" line. So it really didn't upgrade for some reason.

[legoktm]

The staging job passed over the weekend so this is correlated to some specific updates provided by Ubuntu... I assume we'll see this again whenever they push some stable update, so leaving this open.