Bug#1125014: dies on unknown architecture in .dsc

[Paul Gevers]

Hi,

On 1/11/26 05:54, Stuart Prescott wrote:
> Perhaps Paul can add 
> some autopkgtest knowledge to this to help too, to know how 
> architecture_is_concerned is being called in this situation.


I just realized that the use of python3-debian for this is a recent 
change [1] (we used Perl, but now only on systems where python3-debian 
is too old). We use it to figure out which binaries we should expect 
from a source on the architecture we're running the test for [2].

Instead of giving the full list to 
dpkg_arch_table.architecture_is_concerned(), we could ask it one 
architectures at a time and handle the exception ourselves (and assume 
the answer is False for that arch), but that feels clumsy. Given that we 
aim to be backwards compatible for a long time [3], I think we still 
should do that. I'd still like python3-debian to do that for us, such 
that eventually we can drop such backwards-compatibility code.

Paul


[1] 
https://salsa.debian.org/ci-team/autopkgtest/-/commit/dd84a47ebaf68b64c8e6a46b67946418c6e6a0e8
[2] 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/lib/testdesc.py?ref_type=heads#L376
[3] 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/debian/README.source

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-python-debian-maint/attachments/20260111/4e6cb755/attachment.sig>