On Wed, Jan 23, 2008 at 11:29:10AM -0800, Vagrant Cascadian wrote: > Package: gjdoc > Version: 0.7.8-7 > Severity: normal > > when upgrading gjdoc in a chroot environment without /proc mounted, i > get the following string of errors: > > Preparing to replace gjdoc 0.7.8-6 (using .../gjdoc_0.7.8-7_i386.deb) ... > Unpacking replacement gjdoc ... > GC Warning: Couldn't read /proc/stat > Couldn't read /proc/self/stat > dpkg: warning - old post-removal script returned error exit status 2 > dpkg - trying script from the new package instead ... > GC Warning: Couldn't read /proc/stat > Couldn't read /proc/self/stat > dpkg: error processing /var/cache/apt/archives/gjdoc_0.7.8-7_i386.deb > (--unpack): > subprocess new post-removal script returned error exit status 2 > GC Warning: Couldn't read /proc/stat > Couldn't read /proc/self/stat > dpkg: error while cleaning up: > subprocess post-removal script returned error exit status 2 > Preparing to replace coreutils 5.97-5.7 (using .../coreutils_6.10-1_i386.deb) > ... > Unpacking replacement coreutils ... > Errors were encountered while processing: > /var/cache/apt/archives/gjdoc_0.7.8-7_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > it would be nice if gjdoc didn't require /proc to be mounted during > upgrades.
Thats not gjdoc's fault. gjdoc uses gcj-dbtool to register/deregister its classes. This tool needs /proc/stat. Cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
