Package: sbuild Previous-Subject: Re: seccomp woes Original-To: debian-devel@lists.debian.org On Fri, Jul 19, 2019 at 11:28:36PM -0300, gregor herrmann wrote: > On Sat, 20 Jul 2019 00:21:10 +0200, Christoph Biedl wrote: > > > * Centralize the list of supported archs in the seccomp packages. By > > either creating an empty libseccomp-dev for the archs where seccomp > > is not supported, or by creating a "libseccomp-dev-dummy" for these. > > In the latter case package maintainers would have to do a one-time > > change of the build dependency into "libseccomp-dev | > > libseccomp-dev-dummy" and can focus on other issues then. > > AFAIK this won't work because sbuild on the buildds is configured to > only use the first alternative from a list of build dependencies. Reported as bug. Not checked if it already was reported before. Not checked if it really fails when it can't find the first alternative from list of build dependencies. Thing is that sbuild _might_ be blocking a nice way to cope with libraries that are not available on all architectures. Context at https://lists.debian.org/debian-devel/2019/07/msg00405.html Groeten Geert Stappers -- Leven en laten leven
Attachment:
signature.asc
Description: PGP signature