Bug#670597: marked as done (libc6: /lib/ld-linux.so.3 symlink not set)
Your message dated Fri, 27 Apr 2012 12:04:29 +0000
with message-id <20120427120428.GH11905@0c3.net>
and subject line libc6: /lib/ld-linux.so.3 symlink not set
has caused the Debian Bug report #670597,
regarding libc6: /lib/ld-linux.so.3 symlink not set
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
670597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670597
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.13-30
Severity: grave
Dear Maintainer,
In debugging why /usr/sbin/samhain returned 'No such file or directory', it became
evident that the symlink in the subject line is not set:
lfilipoz@hasse:~$ ldd /usr/sbin/samhain
...
/lib/ld-linux.so.3 => /lib/ld-linux-armhf.so.3 (0xb6f51000)
...
lfilipoz@hasse:~$ ls -l /lib/ld-linux.so.3
ls: cannot access /lib/ld-linux.so.3: No such file or directory
Thanks,
Luca
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: armhf (armv7l)
Kernel: Linux 3.2.0-2-mx5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6 depends on:
ii libc-bin 2.13-30
ii libgcc1 1:4.7.0-3
libc6 recommends no packages.
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.42
ii glibc-doc <none>
ii locales-all [locales] 2.13-30
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Closing this bug, as it was discovered that the failing binaries
in question were from debian-ports, not from debian.org. Maintaining
backward compat with non-official archives is a non-starter, and
hopefully most people know how to work around this with violent
apt-pinning sidegrades, or reinstalling from the official archive.
... Adam
--- End Message ---
Reply to: