On Wed, May 15, 2013 at 01:57:25AM +0200, Thibaut VARENE wrote:
> Package: e2fsprogs
> Version: 1.42.5-1.1
> Severity: grave
> Justification: renders package unusable
#1) This looks to be ia64 specific. This is the output of ldd
/sbin/fsck.ext3 on an x86-64 platform:
linux-vdso.so.1 (0x00007ffffeb1a000)
libext2fs.so.2 => /lib/x86_64-linux-gnu/libext2fs.so.2
(0x00007f437aa07000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2
(0x00007f437a803000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
(0x00007f437a5db000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f437a3d6000)
libe2p.so.2 => /lib/x86_64-linux-gnu/libe2p.so.2 (0x00007f437a1ce000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4379e20000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f4379c04000)
/lib64/ld-linux-x86-64.so.2 (0x00007f437ac68000)
#2) We need to determine whether it's /sbin/fsck.ext3 or one of its
shared libraries which is depending upon which is pulling in
libunwind.
Can you run the command "objdump -p /sbin/fsck.ext3 | grep
NEEDED"? On my x86-64 system, this is what I see:
NEEDED libext2fs.so.2
NEEDED libcom_err.so.2
NEEDED libblkid.so.1
NEEDED libuuid.so.1
NEEDED libe2p.so.2
NEEDED libc.so.6
Then do a recursive expansion of each of the libraries which you
see, i.e. replace /sbin/fsck.ext3 with /lib/*/libblkid.so.1, etc.
Thanks,
- Ted
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
