[buildd-tools-devel] Bug#893608: sbuild: Silent arch:all defaults change breaks buildd setups

Michael Stapelberg stapelberg at debian.org
Wed Mar 21 17:28:16 UTC 2018


control: tags -1 + pending

Hi James,

James Clarke <jrtc27 at debian.org> writes:
> In the latest upload, #870263 was fixed (which I support, for what it's worth;
> any+all builds is the right default for users), meaning that buildd setups now
> build arch:all packages, which we *have* to work around by setting
> $build_arch_all=0 in sbuild.conf. Without this, uploads are rejected by the
> archive (the buildd's signing key does not have upload rights for arch:all
> packages, the arch:all packages already exist, etc). This is therefore a
> breaking change, and so deserves at least a mention in the NEWS file. Moreover,
> having to configure this in sbuild.conf is sub-optimal; ideally, buildd would
> pass --no-arch-all to sbuild when an arch:any build is requested by wanna-build;
> as far as I know, the assumption is always that a non-Architecture:all build is
> arch:any.

Addressed by the following commit IIUC:
https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=821144b5ef48bb11bf98657349ba808c25452721

> We probably also don't want lintian run during buildd builds as it fork-bombs on
> packages like gcc-8-cross-ports (#890873), and there's lintian.debian.org doing
> that for x86, which is probably good enough, though I suppose in an ideal world
> it would be run too.

https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e8da1ee764d8b3b5aaa0fe82aac8e877f1cc4f4d

-- 
Best regards,
Michael



More information about the Buildd-tools-devel mailing list