I think you can use the buildplace option for your liking. At Sat, 10 Sep 2011 15:07:44 +0200, J$(D+S(Brg Sommer wrote: > > Package: cowbuilder > Version: 0.64 > Severity: normal > > Hi, > > I'm running cowbuilder in a Linux Container which has its own process ID > space. Therefore, each build starts with the same pid and cowbuilder uses > the same directory cow.2 for each build. Hence, no parallel builds are > possible, because they all want to use cow.2. > > # lxc-execute -n cowbuilder-update -- cowbuilder --update > -> Copying COW directory > forking: rm -rf /var/cache/pbuilder/build//cow.2 > forking: cp -al /var/cache/pbuilder/base-sid.cow > /var/cache/pbuilder/build//cow.2 > I: removed stale ilistfile /var/cache/pbuilder/build//cow.2/.ilist > -> Invoking pbuilder > forking: pbuilder update --buildplace /var/cache/pbuilder/build//cow.2 > --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.2 > cow-shell > > Please, use mktemp or something to choose a unique name to reduce these > collisions. > > Bye, J$(D+S(Brg. > > -- System Information: > Debian Release: unstable/experimental > APT prefers unstable > APT policy: (900, 'unstable'), (700, 'experimental') > Architecture: powerpc (ppc) > > Kernel: Linux 3.1.0-rc3.ledtest-00161-g671ee7f-dirty > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages cowbuilder depends on: > ii cowdancer 0.64 > ii libc6 2.13-20 > ii pbuilder 0.202 > > cowbuilder recommends no packages. > > cowbuilder suggests no packages. > > -- no debconf information
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
