'high' severity package used 'medium' delay for migration

[JonathonHall-Purism]

gnome-settings-daemon 44.1-1pureos2 was published with severity 'high' in landing, but the migration status says that it needs to be 5 days old to migrate. I expected it to be 2 days, since that's the delay configured for 'high'; 5 is for 'medium'.

The migration is currently here (screenshot below): https://master.pureos.net/migrations/excuse/63dd9edc-520d-4075-bc56-544f2e349bb4

Here's the config where I think 'high' should be 2 days: https://source.puri.sm/pureos/infra/pureos-laniakea-config/-/blob/main/config/spears-tasks.toml

Changelog with 'high' priority for 44.1-1pureos2: https://source.puri.sm/Librem5/debs/gnome-settings-daemon/-/blob/pureos/latest/debian/changelog

Screenshot of migration:

[ximion]

I've looked through the code, and I see no way how this could possibly be happening...
Laniakea reads the Urgency field of a changes file, and if none exists, assumed low as priority. Since this upload has medium priority one of two things must have happened:

• The changes_urgency property could not have been set at all (in which we assume medium by default)
• The changes file did contain medium for its Urgency field, even though the changelog contained high

When a package is accepted, there is only one codepath this can take, in which the changes_urgency is overridden unconditionally. So, at the moment I assume the reason for this is the second one, which wouldn't make it a Laniakea issue, but a builder issue. How was this package built?

I think at the moment we can only keep this bug report open and monitor the situation, and see if this happens again (potentially adding more logging if needed).

[dos1]

I've seen this happening with a package that got accepted out of the NEW queue.

[dos1]

Now got a package that did not go through the NEW queue and yet Laniakea ignored the urgency set in the changes file:

Format: 1.8
Date: Sun, 18 Jan 2026 18:59:49 +0100
Source: linux-librem5
Architecture: source
Version: 6.6.119pureos1~byz2
Distribution: byzantium
Urgency: critical
Maintainer: Purism Kernel Team <kernel@puri.sm>
Changed-By: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Changes:
 linux-librem5 (6.6.119pureos1~byz2) byzantium; urgency=critical
 .
   * Revert "librem5_defconfig: Enable virtualization-related options"
   * Revert "librem5_defconfig: Enable features recommended by systemd"
Checksums-Sha1:
 bf4e36bd7b2259beb1d5c4aa5e1970dfa27a6c25 2214 linux-librem5_6.6.119pureos1~byz2.dsc
 edf62ff74451411b25b16a5939a2e214c5d36fee 141005428 linux-librem5_6.6.119pureos1~byz2.tar.xz
 b4aa697281f3b5306f9eb84f102b5897ed584fd0 6979 linux-librem5_6.6.119pureos1~byz2_source.buildinfo
Checksums-Sha256:
 f8ba2f46b8e691c41ca0826039314da7e7718ab092f1480fde5066608efdcf14 2214 linux-librem5_6.6.119pureos1~byz2.dsc
 afac34794672153799c74f32ecf4831e9b40ae09af37893bc64b7175f476f758 141005428 linux-librem5_6.6.119pureos1~byz2.tar.xz
 eaa222d0cfab014c0be04fa11d85b9b6f789a14429cc8d83ec4558460f484e98 6979 linux-librem5_6.6.119pureos1~byz2_source.buildinfo
Files:
 c7d853b6b24985884da89c11ef73a771 2214 kernel optional linux-librem5_6.6.119pureos1~byz2.dsc
 80eaee1ad7a4b38a3b89061bc23b7fdf 141005428 kernel optional linux-librem5_6.6.119pureos1~byz2.tar.xz
 068b8ecfc85328b372d153fe8c1393d0 6979 kernel optional linux-librem5_6.6.119pureos1~byz2_source.buildinfo

* Migration status for linux-librem5 (6.6.119pureos1~byz1 to 6.6.119pureos1~byz2): Waiting for test results or another package, or too young (no action required now - check later)
* Too young, only 0 of 8 days old

delays = {low=10, medium=8, high=4, critical=1, emergency=0}