Hi,

An additional patch to make this thing work.

--- pbuilder-buildpackage       20 Jun 2005 10:39:45 -0000      1.112
+++ pbuilder-buildpackage       25 Jun 2005 06:27:34 -0000
@@ -32,7 +32,7 @@
 fi;
 
 if [ -n "$BUILDUSERNAME" -a -n "$BUILDUSERID" ]; then
-    SUTOUSER="su $BUILDUSERNAME -- "
+    SUTOUSER="su -p $BUILDUSERNAME -- "
     DEBBUILDOPTS="$DEBBUILDOPTS -rfakeroot"
     EXTRAPACKAGES="${EXTRAPACKAGES} fakeroot"
     echo "I: using fakeroot in build."


regards,
        junichi


At Fri, 24 Jun 2005 13:43:08 +0300,
Brian Nelson wrote:
> 
> On Fri, Jun 24, 2005 at 07:55:10AM +0900, Junichi Uekawa wrote:
> > > > --- pbuilder-buildpackage       21 Apr 2005 23:10:23 -0000      1.111
> > > > +++ pbuilder-buildpackage       20 Jun 2005 10:38:50 -0000
> > > > @@ -87,7 +87,6 @@
> > > >  fi
> > > >  
> > > >  echo " -> Building the package"
> > > > -export PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin"
> > > 
> > > This is around where you have to set the PATH (right after $CHROOTEXEC).
> > > If you set the PATH before $CHROOTEXEC (e.g. when the pbuilderrc is
> > > sourced like below), it'll just get clobbered by $CHROOTEXEC...
> > 
> > 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.
> 
> -- 
> Society is never going to make any progress until we all learn to
> pretend to like each other.
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to