needed-package-updates prevents us from making our own backports
While working on !1209 (merged) I backported Debian Sid's cryptsetup 2:2.6.1-5 to bullseye, which Tails currently is based on. So using the usual version scheme for a backport we get version 2:2.6.1-5~deb11u1, but then needed-package-updates
complains:
INFO: Need to upgrade to a new APT snapshot:
- cryptsetup (2:2.6.1-5~deb11u1) to Debian sid (2:2.6.1-5)
IMHO this backport should result in no complaints.
Related, since there is a 2:2.6.1-4~deb12u1 backport for Debian bookworm, if I had backported 2:2.6.1-4 I would get this:
INFO: Need to upgrade to a new APT snapshot:
- cryptsetup (2:2.6.1-4~deb11u1) to Debian bookworm (2:2.6.1-4~deb12u1)
which IMHO also shouldn't happen.
But let's say that we had a custom backport 2:2.6.1-4~deb11u1 but we update out APT snapshots and Sid gets the update 2:2.6.1-5, then I'd like this complaint:
INFO: Need to build and upload new backports:
- cryptsetup (2:2.6.1-4~deb11u1) has a newer version in Debian sid (2:2.6.1-5)