Hi, I was thinking about that too. One problem with cleaning up is that you can be bind-mounting something inside chroot, so it's not safe to do weekly.
It's probably safe to run pbuilder clean in one of the boot scripts, which will save a lot of people from having to type 'pbuilder clean' from time to time. Or, a policy of cleaning directories which have existed since before the last reboot might be a good idea. Something along the lines of /etc/init.d/pbuilder-clean .... At Wed, 25 Feb 2009 11:17:34 +0100, Stefano Zacchiroli wrote: > > Package: cowbuilder > Version: 0.49 > Severity: wishlist > > $ ls /srv/debian/pbuilder/build/ > cow.13333 cow.1338 cow.13924 cow.14500 cow.25161 cow.29308 cow.5684 > > This happens to me quite often, I guess it is because sometimes I > press CTRL-C to interrupt a build which I discover was not > needed. More generally, I imagine it can happen for various reasons > when cowbuilder got killed. > > Can you please consider adding a way, maybe an /etc/cron.d, entry, > which cleans up old/stale cowbuilder directories? > > Many thanks for cowbuilder, it rocks my developer life! > Cheers. > > -- System Information: > Debian Release: 5.0 > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages cowbuilder depends on: > ii cowdancer 0.49 Copy-on-write directory tree > utili > ii libc6 2.9-3 GNU C Library: Shared libraries > ii pbuilder 0.186 personal package builder for > Debia > > 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
