Riku Voipio <[EMAIL PROTECTED]> writes: > On Wed, May 07, 2008 at 08:13:20PM +0300, Niko Tyni wrote: >> On Wed, May 07, 2008 at 01:38:41PM +0200, Lucas Nussbaum wrote: >> > It seems that this is caused by the fact that schroot logs in the user > >> > with $HOME set to the host's pwent, not the guest. My config is: >> > host: >> > user's home: /home/user >> > chroot: >> > user's home in /etc/passwd: /nonexistent (which doesn't exist) > > This appears to be the case here as well. > >> 5.0.10-9 built OK on arcadelt. Cc'ing the armel buildd maintainers; I >> suppose the setup on ALL6500 should be changed. > > ALL6500 uses schroot while other buildd's use sudo.
Wow, I didn't realise anyone was using it in a real buildd environment yet! Does this mean you're using buildd-tools sbuild as well? If so, have you come across any issues with it? (I have no knowledge of anyone else using it in this way, so I am really interested to know of any testing as a buildd). > As a workaround I can > change buildd's $HOME to match inside schroot to the one outside > (/home/buildd) and reschedule perl. > > I believe /nonexistent is used to catch packages trying to write to > $HOME during builds. Does this not lead to problems for packages which attempt to read files from $HOME during a build? Are there any cases where this is a problem? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
pgp1KTzbywLzB.pgp
Description: PGP signature
