Hi Paul, On Thu, Oct 17, 2024 at 09:35:17AM +0200, Paul Gevers wrote: > I'm not sure if this idea came up before, but as far as I can see there is > no bug open about it and last time I checked dpkg didn't support the > following idea.
I've seen this idea frequently, but do not remember any concrete instance at this time. > In autopkgtest [1], I added support in the testing control file to > explicitly mention unsupported architectures. This means that instead of > listing all supported architectures, one can say something like: > Architecture: !s390x > which means the same as '`any` but not on s390x', just like in > (Build-)Depends. I note that the Architecture field in the binary package serves subtly different purpose. Effectively, there are three distinct purposes that we currently accomplish with this field: * Determine whether a binary package is all/indep or any/arch. * Determine on which architectures a binary package is to be emitted. * Skip building packages when unsupported. You are mainly targeting the last purpose here. If your package has many binary packages, repeating this information quickly becomes tedious. The alternatives suggested thus far are: * Build-Depends: architecture-is-64bit * Build-Depends: unsupported-architecture [s390x] I agree that this is not super obvious, but it technically works right now in a practical way. Helmut
