Version: 0.215+nmu4 Re: Junichi Uekawa 2009-06-27 <87y6re2dsl.dancerj%[email protected]> > > 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.
Hi, any chance to get this fixed? I just ran into it, and the error messages printed are pretty misleading. adt-run [22:52:35]: test connect: [----------------------- Creating new cluster 9.4/regress ... config /etc/postgresql/9.4/regress data /var/lib/postgresql/9.4/regress locale C.UTF-8 cowdancer: cannot open ilistfile /.ilist cowdancer: Fatal, initialize_functions failed cowdancer: cannot open ilistfile /.ilist cowdancer: Fatal, initialize_functions failed cowdancer: cannot open ilistfile /.ilist Error in GnuTLS initialization: Failed to acquire random data. cowdancer: cannot open ilistfile /.ilist cowdancer: Fatal, initialize_functions failed cowdancer: cannot open ilistfile /.ilist initdb: could not look up effective user ID 101: Cannot allocate memory Error: initdb failed Stopping cluster 9.4/regress... Error: specified cluster does not exist adt-run [22:52:36]: test connect: -----------------------] (pgbouncer autopkgtest run) Christoph -- [email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
