On Wed, Feb 22, 2012 at 12:29:09AM +0100, Andreas Beckmann wrote: >Package: fake-hwclock >Version: 0.2 >Followup-For: Bug #659254 > >Hi, > >fake-hwclock 0.2 still has errors from the cronjob, at least in a setup >which did > bootstrap testing > install fake-hwclock 0.1 > distupgrade unstable (installs fake-hwclock 0.2) > remove fake-hwclock > >0m31.0s INFO: Package fake-hwclock contains cron file: >/etc/cron.hourly/fake-hwclock >0m31.0s DEBUG: Starting command: ['chroot', >'/org/piuparts.debian.org/tmp/tmpjwIOkK', 'eatmydata', >'/etc/cron.hourly/fake-hwclock'] >0m31.0s ERROR: Command failed (status=127): ['chroot', >'/org/piuparts.debian.org/tmp/tmpjwIOkK', 'eatmydata', >'/etc/cron.hourly/fake-hwclock']
It's no longer going to complain (and cause error messages). Does the exit code matter? -- Steve McIntyre, Cambridge, UK. st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
