[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Build failed in Jenkins: dpkg-binaries » i386 #228


* Guillem Jover [Sun Aug 10, 2014 at 09:17:02AM +0200]:
> On Sun, 2014-08-10 at 08:49:52 +0200, Jenkins Team at Grml wrote:
> > See <http://jenkins.grml.org/job/dpkg-binaries/architecture=i386/228/>

> > I: Building the package
> > W: no hooks of type A found -- ignoring
> > I: Running cd tmp/buildd/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" dpkg-buildpackage -us -uc  -B -B -rfakeroot
> > dpkg-buildpackage: cannot combine -B and -B

> > Use --help for program usage information.
> > E: Failed autobuilding of package
> > I: user script /srv/pbuilder/build/cow.28879/tmp/hooks/C10shell starting

> I'm pondering about fixing this in dpkg to at least allow the same option
> to be specified multiple times for backward compat, but I'm wondering why
> is the script passing it twice? Could that be fixed there?

The -B option is set in this jenkins-debian-glue run for:

1) Host architecture [amd64] does not match build architecture [i386]
2) The package provides arch 'all' + 'any', so we're enabling the -B
   buildoption for the i386 arch build (since the main build is the
   one for amd64)

That's also why the amd64 build works fine (no -B option) but just
the i386 one (-B -B) fails. I could of course unify the options used
in the final jenkins-debian-glue cmdline, but a backward compat fix
would be very much appreciated as I noticed that other users
(outside of jenkins-debian-glue) ran into this very same issue.

Thanks, Guillem!


Attachment: signature.asc
Description: Digital signature

Reply to: