Hi,

cowbuilder manpage says that:

severity 579506 minor
retitle  579506 --configfile option doesn't pick non standard options from original config files
thanks

Hmhm, sorry, I take that back. Only the non-standard options defined
in .pbuilderrc are not taken in the file passed by --configfile.

For example I define in .pbuilderrc

arch="amd64"
DISTRIBUTION=sid
BASEDIR=$HOME/debian/pbuilder
BASEPATH=$BASEDIR/base-${DISTRIBUTION}-${arch}.cow

and in .pbuilderrc-experimental-amd64 I do:

DISTRIBUTION=experimental
BASEPATH=$BASEDIR/base-${DISTRIBUTION}-${arch}.cow

then dumpconfig shows:
  basepath: /base-experimental-amd64.cow

while if I redefine BASEDIR=$HOME/debian/pbuilder
in .pbuilderrc-experimental-amd64 it does work fine.

I guess it makes sense, but it'd be nice if all the variables where
taken from the original config file. I know the manpage says unknown
options are ignored, but the current behavior (which ignores them but
treat them correctly when they are used to defined known options) is
really helpful.

Thanks for your attention :)

Hi,

Okay, that's a different behavior for cowbuilder vs pbuilder. I'm not
sure what would ultimately be a desirable way to do it.

At Wed, 28 Apr 2010 08:45:14 +0200,
Yves-Alexis Perez wrote:

It looks to me like a good idea. Here, I'm fighting with the fact that
pbuilder now wants to use trusted apt sources, which is a pain since I'm
using $BUILDRESULT as a source and I don't really want to sign that
everytime I rebuild a package.

So I'd like to tune PBUILDERSATISFYDEPENDSOPT or APTGETOPT but it seems
they won't be used by cowbuilder for some reason.

I guess cowbuilder doesn't call pbuilder with --configfile (maybe for
good reasons though) because adding those options to $HOME/.pbuilderrc
seems to fix the problem.

Cheers,