[Bug 326216] Re: Bug#514358: pdebuild host --debbuildopts inherited by target pbuild

Mattia Rizzolo mattia at mapreri.org
Mon May 16 00:19:41 UTC 2016

tag 514358 wontfix
 status invalid

On Mon, Feb 09, 2009 at 12:02:03AM +0900, Junichi Uekawa wrote:
> IMO, That's a feature, not a bug.

me too.

> I don't want to accept this patch.

Me neither.

                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

** Changed in: pbuilder (Ubuntu)
       Status: Incomplete => Invalid

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pbuilder in Ubuntu.

  pdebuild host --debbuildopts inherited by target pbuild

Status in pbuilder package in Ubuntu:
Status in pbuilder package in Debian:

Bug description:
  Binary package hint: pbuilder

  This is a latent bug, exposed as a by-product of the fix I created for
  bug #278213 "Does not accept multiple --debbuildopts options" which
  resulted in "pbuilder (0.181ubuntu6)".

  The problem is that when using pdebuilder and passing --debbuildopts
  to both 'sides' (host and target), the target pbuilder dpkg-source
  incorrectly inherits the host --debbuildopts.

  For example:

   HOST_DEB_OPTIONS="--debbuildopts -i -I" 
   PBUILDER_DEB_OPTIONS="--debbuildopts -Idebian/dpkg-source.excludes"

  results in the inner dpkg-source seeing:

   dpkg-source -i -I -Idebian/dpkg-source.excludes -b kvm-83+dfsg

  Which in Hardy and later isn't a problem (since -I is acceptable to
  dpkg-source >= v1.14.7). However, if working on back-porting a package
  to Gutsy or Feisty or Edgy the versions of dpkg-source in those
  releases do not understand the -I option without a file specification

  This will cause the target pbuild to fail since the source can't be

  This wouldn't have come to light if it wasn't for my desire to back-
  port some packages for use on long-lived servers that are running
  stable older releases. In these cases my build_test script generates
  two different sets of --debbuildopts for the host (more recent) and
  target (older) dpkg-source.

  The builds were failing and as can be seen in the example above it is
  because the host's --debbuildopts are passing to the target.

  Patches to follow.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list