Bug#462292: gjdoc: fails to upgrade when /proc is not mounted
Vagrant Cascadian
vagrant+debianbugs at freegeek.org
Wed Jan 23 19:29:10 UTC 2008
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.
live well,
vagrant
More information about the pkg-java-maintainers
mailing list