Hi,
> > Now I don't grok you.
> > $CHROOTEXEC is just 'chroot' which shouldn't have any effect on
> > the environmental variable which the shell is holding.
>
> Err, yeah, sorry. It's not CHROOTEXEC, it's PBUILDERROOTCMD (sudo, su,
> etc.) that munges the PATH.
>
> > Removing this PATH over to the pbuilderrc config file which
> > is sourced at the top of pbuilder-buildpackage should fix what you're
> > experiencing.
> >
> > ... but that's not happening.
> >
> > Hmm...
>
> Ah, it's because the pbuilderrc is sourced in pdebuild (via
> pbuilder-checkparams) *before* the ${PBUILDERROOTCMD} pbuilder stuff...
> It should work if you set PBUILDERROOTCMD="" run the whole
> /usr/bin/pdebuild as root.
The file pbuilderrc is also sourced in pbuilder,
pbuilder-buildpackage -> pbuilder-checkparams -> pbuilder-loadconfig.
After tracking echo's, it's probably overridden there..:
+ echo 'cd tmp/buildd/*/; dpkg-buildpackage -us -uc -rfakeroot'
+ chroot /var/cache/pbuilder/build//18157 su pbuilder -- /bin/bash
Actually, I've checked, it's 'su' who's munging input.
It probably needs to be passed '-p' option to preserve
env-var.
regards,
junichi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
