On Wed, May 07, 2008 at 07:01:31PM +0100, Roger Leigh wrote: > 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).
This buildd was set up before armel was taken as part of debian buildd network, and I was new at the nuances of setting up buildds.. Your versions of sbuild/schroot have been working fine (this is the first issue so far) so I haven't bothered reconfiguring them. For later buildd's managed under the debian.org system administration I used older versions just in case. > > 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? Well it would quite clearly be a bug if a tool failed to work if it can't read a file from $HOME during build.. notice that /nonexistent passwd entry is created from the buildd-make-chroot script from buildd package. So this is a very old practice, and has rarely caused problems. I think qmake used to be problematic in this matter.
signature.asc
Description: Digital signature
