tag:blogger.com,1999:blog-1134723925265805427.post2984080281394228479..comments2023-10-31T14:04:04.105+02:00Comments on Rambling around foo: HOWTO: Things to remember about cowbuilder eddyphttp://www.blogger.com/profile/13986125106284142716noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1134723925265805427.post-88334677348858327532012-08-25T13:42:55.112+03:002012-08-25T13:42:55.112+03:00Good catch about BUILDRESULT, but I usually just p...Good catch about BUILDRESULT, but I usually just put the cowbuilding user into a group and chgrp and chmod g+sw it.<br /><br />In my multi-{arch,distro} cowbuilder ~/.pbuilderrc – https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/pbuilderrc?rev=HEAD – I have hardcoded BUILDRESULTUID and BUILDRESULTGID, but it’s probably possible to use something like $SUDO_UID and $SUDO_GID if set (after all, pbuilder runs this file using GNU bash).<br /><br />I also put some notes into https://www.freewrt.org/~tg/dp/0-NOTE.txt and https://www.freewrt.org/~tg/dp/files/ like wrapper scripts around cowbuilder that use eatmydata, for things like updating (eW cowbuilder --update), logging in with and without saving, building packages with and without source and just arch:any (for porter uploads) and mention things like you want™ to create the pbuilder user ($BUILDUSERID, $BUILDUSERNAME) also *outside* the chroot, touch /CurrentlyBuilding and pimp debconf to avoid man-db updates inside, that building apr wants /dev/shm (oh well, /run/shm now probably?) bind-mounted, and other things out of the life of a “human” Debian-Ports build “dæmon” (who prefers cowbuilder over sbuild any time of the night).<br /><br />If I can help with cowbuilder, ping me on IRC (Freenode, mirabilos).Anonymousnoreply@blogger.com