Hi,
At Wed, 24 Jun 2009 23:38:37 +0800,
Paul Wise wrote:
>
> [1 <text/plain (quoted-printable)>]
> On Wed, 2009-06-24 at 23:42 +0900, Junichi Uekawa wrote:
>
> > Do you have BUILDUSERNAME set so that you are running on non-root user?
>
> Doesn't look like it:
>
> p...@chianamo:~$ env | grep BUILDUSER
> p...@chianamo:~$ grep -ri BUILDUSER /etc/pbuilder* ~/.pbuilder*
>
> > '$CHROOTEXEC $SUTOUSER' might in fact not have access to .ilist file,
> > if .ilist file is not readable by that user.
>
> Hmmmm.
>
> > Or do you have 'su' configured in such a way that is different from
> > default Debian installation?
>
> I don't think so.
>
> I do use a umask of 0027. After changing it to 022 the build works fine
> again. Not sure what the appropriate action is here, would it be
> possible to make pbuilder/cowbuilder work with a umask of 027? Perhaps
> the script could fix the umask to make written files world-readable?
Great, so we found the problem.
Most of pbuilder / cowbuilder is running as root and create some files
as root, but when building packages and becoming non-root, the files
need to be read by that user, so 0027 isn't really tested/supported in
the current cowbuiler codebase.
pbuilder actually sets umask to 0022. cowbuilder doesn't, so the
quick correct course of action would be to set umask to 0022 inside
cowbuilder.
Getting pbuilder / cowbuilder to work with 0027 would be a more
involved change.
regards,
junichi.
--
dan...@{netfort.gr.jp,debian.org}
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
