Hi,
> > > Building a package with "sudo pbuilder build --buildtarget foo" puts
> > > files in foo that are owned by user 1234, group 1234 (neither of which
> > > exists on the system). (Without --buildtarget they are put
> > > in /var/cache/pbuilder/result, but the same uid/gid). This seems
> > > strange.
> >
> > This is due to pbuilder now running inside fakeroot by default. The
> > default value '1234' (randomly picked) can be anything that isn't used
> > by other user, so pbuilder session will have a hard time interacting
> > with outside of chroot.
>
> I'm not sure I understand why the uid of the person who invoked pbuilder
> can't be used, or why pbuilder (which is run as root) can't chown the
> resulting files to the person who invoked it. (See $SUDO_UID and
> $SUDO_GID.)
The main reason that was not done so far is that you can be root
without using sudo, and this option wasn't default so this part was
overseen.
That's another heuristics that I could add to default pbuilder
which might or might not satisfy everyone's needs.
The most reasonable default value would probably be
export BUILDRESULTUID=${SUDO_UID:-0}
export BUILDRESULTGID=${SUDO_GID:-0}
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
