Hi! On 2023-08-21 07:36, Adam Borowski wrote: > On Mon, Aug 21, 2023 at 10:38:52AM +0200, Emanuele Rocca wrote: > > Well FTBFS is a bug isn't it? :-) > > A FTBFS on an architecture that has built before (and hasn't been RMed) > is a bug, and one that's policied as high severity.
As far as I understand that is the case for birdtray on all 3 architectures? It used to build fine in the past, now it does not: https://buildd.debian.org/status/fetch.php?pkg=birdtray&arch=mipsel&ver=1.4-2&stamp=1547097073&raw=0 > Obviously we'd prefer thunderbird:armhf to be a thing, but unless/until it > can be fixed, talk about thunderbird addons on armhf is quite moot. Agreed. > > Why does birdtray build-depend on thunderbird? It seems to build > > perfectly fine in a clean armhf chroot without it. > Build yes, work no. The result would be a pointless package you can't > use; adding this (otherwise superfluous) build-dependency avoids > having a non-installable package in the archive. Given that we know that birdtray does not work on armhf, armel, and mipsel, the Architecture field should reflect this fact I think. And yes I understand that in a hypothetical scenario in which thunderbird works on those arches, birdtray works too. That's not the present reality though and it seems more accurate to state this fact explicitly instead of implying it with a superfluous uninstallable build-dep. >From >https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture: | Specifying a list of architectures or architecture wildcards indicates | that the source will build an architecture-dependent package, and will | only work correctly on the listed or matching architectures. Cheers, Emanuele
