Hi, On Tue, 12 Aug 2014, Ansgar Burchardt wrote: > First, w-b has to recognize that arch:all packages need to be built. > And they need to be scheduled on a buildd which builds the arch:all > packages (and only the arch:all packages?). > > For the latter I assume sbuild would need an option to build only the > arch:all packages using dpkg-buildpackage -A. It would also be > interesting to test which packages FTBFS in this case.
FWIW, sbuild supports "-A" (--arch-all) and this will result in calling dpkg-buildpackage -b (instead of -B). On Wed, 13 Aug 2014, Colin Watson wrote: > I don't think there's a good reason to build them separately, and some > good reasons not to (for example, it would waste a good deal of buildd > time for a number of packages without very hygienic separation of their > build rules). My suggestion would be to just build them along with the > architecture-dependent binaries for some nominated architecture, which > could be package-specific or not depending on what you all have time > for, and be done with it. +1 In kali, that's exactly what I have been doing. Any package that builds an arch: all is sent to an amd64 buildd and sbuild on the amd64 buildd gets called with -A. It doesn't matter whether it builds only the arch: all or another package too. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140813123433.gb6...@x230-buxy.home.ouaza.com
