On 2019-07-20 07:58, Johannes Schauer wrote: > No it does not block this. The sbuild configuration variable > $resolve_alternatives or the command line option --resolve-alternatives allows > one to enable or disable that sbuild only uses the first alternative. > > As Gregor also correctly wrote, the problem is not sbuild but how sbuild is > configured on the buildds.
This is indeed something configurable at the wanna-build level. > You might want to re-assign the bug to the buildd admins if you really want to > propose that the handling of alternatives is changed. This is done on purpose in order to provide stable features over time. If a package build-depends on foo | bar and foo is temporarily uninstallable (for example due to a transition or a version mismatch between arch:all and arch:any) bar will be used instead, possibly disabling some features in the package. In the file & libseccomp example, it means seccomp support might be silently disabled. Note that for backports, alternatives are considered, as the above is very unlikely to happen. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
signature.asc
Description: PGP signature
