Hi,
On Sat, Oct 30, 2021 at 10:39:19AM -0400, Rich wrote:
> I see, so "kernel package in oldstable-backports is unusable" is not a bug.
>
> Is there any way I can view why it's been sitting for so long that
> this happened, or any estimate on how much longer it'll be broken?
I did ping yesterday backports FTP masters team. The problem here is:
the packages need in meanwhile be processed multiple times, very
roughtly, first the backports FTP masters need to flag the package to
be accepted, then the packages (unsigned) are built, next the main FTP
masters need to process the packages for signing, but given the nature
of the packages the linux-signed-{amd64,i386,arm64} source packages
needs another manual processing.
This is all not very smooth, and this time I guess it went longer than
usual.
$ rmadison linux-signed-arm64
linux-signed-arm64 | 4.19.118+2+deb10u1~bpo9+1 | stretch-backports | source
linux-signed-arm64 | 4.19.194+2 | buster-updates | source
linux-signed-arm64 | 4.19.194+3 | oldstable | source
linux-signed-arm64 | 4.19.208+1 | oldstable | source
linux-signed-arm64 | 5.10.46+4~bpo10+1 | buster-backports | source
linux-signed-arm64 | 5.10.46+5 | stable | source
linux-signed-arm64 | 5.10.70+1~bpo10+1 | backports-policy | source
linux-signed-arm64 | 5.10.70+1 | stable | source
linux-signed-arm64 | 5.14.9+2~bpo11+1 | bullseye-backports | source
linux-signed-arm64 | 5.14.9+2 | testing | source
linux-signed-arm64 | 5.14.12+1 | unstable | source
currently shows that linux-signed-arm64 for 5.10.70+1~bpo10+1 is yet to be
processed from the backports-policy queue.
Regards,
Salvatore
