Bug#892547: [Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build=

2018-03-10 Thread jean-christophe manciot
Package: dpkg Version: 1.19.0.5 Right now, running dpkg-buildpackage --build=any builds all architecture dependent packages, such as: - amd64 - arm64 - m68k - mips - ... My proposal offers a way to build a specific or list of specific architecture dependent packages through:

Bug#892547: marked as done ([Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build=)

2018-03-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Mar 2018 14:06:10 +0100 with message-id <20180310130610.ga22...@thunder.hadrons.org> and subject line Re: Bug#892547: [Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build= has caused the Debian Bug report #892547, regarding [Feature

Bug#892545: --build=any,all and --build=binary are not entirely equivalent: the former does not generate a .changes whereas the latter does

2018-03-10 Thread Guillem Jover
Control: reassign -1 devscripts [ Leaving context for the reassignment. ] Hi! On Sat, 2018-03-10 at 13:01:46 +0100, jean-christophe manciot wrote: > Package: dpkg > Version: 1.19.0.5 > binary is supposed to be an alias for any,all as described by the > dpkg-buildpackage documentation >

Processed: Re: Bug#892545: --build=any,all and --build=binary are not entirely equivalent: the former does not generate a .changes whereas the latter does

2018-03-10 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 devscripts Bug #892545 [dpkg] --build=any,all and --build=binary are not entirely equivalent: the former does not generate a .changes whereas the latter does Bug reassigned from package 'dpkg' to 'devscripts'. No longer marked as found in versions

Bug#892547: closed by Guillem Jover <guil...@debian.org> (Re: Bug#892547: [Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build=)

2018-03-10 Thread jean-christophe manciot
> > No, dpkg-buildpackage or debian/rules, just build the packages > matching the host architecture, not for all architectures. In most cases, you're right. But for instance, for binutils, the "--build=binary" option builds the packages for all architectures: cf. the battached .buildinfo. If