Bug#374029: Build-Depends{,-Indep} as defined is not useful and not followed
On Sat, Sep 01, 2012 at 01:33:34AM -0700, Russ Allbery wrote:
> Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr> writes:
> > On Mon, Aug 27, 2012 at 08:31:50AM -0700, Russ Allbery wrote:
> >> Russ Allbery <rra@debian.org> writes:
>
> >>> The following patch implements the decision of the Debian Technical
> >>> Committee in #629385 to make build-arch and build-indep mandatory.
> >>> Please review. Note that I'm not looking for conventional seconds
> >>> since the Technical Committee has already made a judgement; rather,
> >>> I'm looking for wording review and for confirmation that I've
> >>> implemented the Technical Committee decision properly.
>
> >> This patch has now been merged for the next release. Thanks, everyone,
> >> for the review!
>
> > I like to defer it until wheezy is released. Indeed, the relevant dpkg
> > code has not seen much real life testing and the freeze is not a proper
> > time to experiment which the buildd and build systems in general.
>
> I'm not sure that I understand. The only change in Policy changes
> build-arch and build-indep to mandatory from optional, and that isn't
> something we're doing but rather something the Technical Committee
> decided.
The problematic hook is the following:
+ This split allows binary-only builds to not install the
+ dependencies required for the <tt>build-indep</tt>
+ target and skip any resource-intensive build tasks that
+ are only required when building architecture-independent
+ binary packages.
If you follow this recommendation, your package will potentially FTBFS due to
missing build-dependency on the buildd, unless it has been fixed.
I do not think this has seen real life testing at this stage.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: