Comment 36 for bug 539814
Revision history for this message
| Patrick Welche (prlw1) wrote Re: tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM) | #36 |
I have just hit this problem upgrading from hardy 8.04 to lucid 10.04, so you don't need to go back as far as dapper to see it. I now have a partially upgraded system, and a
aptitude safe-upgrade
gives
Preconfiguring packages ...
tar: ./postinst: Cannot utime: Bad file descriptor
tar: ./preinst: Cannot utime: Bad file descriptor
tar: ./prerm: Cannot utime: Bad file descriptor
tar: ./postrm: Cannot utime: Bad file descriptor
tar: ./conffiles: Cannot utime: Bad file descriptor
tar: ./md5sums: Cannot utime: Bad file descriptor
tar: ./control: Cannot utime: Bad file descriptor
tar: .: Cannot utime: Bad file descriptor
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
Tar version is 1.22-2, and /bin/tar is the same as the binary on another working 10.04.1 system
gnulib is not installed - same as on another working 10.04.1 system
One difference is that the working system has:
> ldd `which tar`
librt.so.1 => /lib/tls/
libc.so.6 => /lib/tls/
whereas the "broken" one has:
# ldd `which tar`
librt.so.1 => /lib/librt.so.1 (0xb7fcc000)
libc.so.6 => /lib/libc.so.6 (0xb7e83000)