Package: lockfile-progs
Version: 0.1.16
Severity: important
Dear Maintainer,
All /usr/bin/lockfile-* binaries on armhf have wrong ELF interpreter. For
example:
$ objdump --full-contents --section=.interp /usr/bin/lockfile-create
/usr/bin/lockfile-create: file format elf32-littlearm
Contents of section .interp:
8134 2f6c6962 2f6c642d 6c696e75 782e736f /lib/ld-linux.so
8144 2e3300 .3.
This renders the package unusable on armhf for most users:
$ /usr/bin/lockfile-create
-bash: /usr/bin/lockfile-create: No such file or directory
$ /lib/ld-linux-armhf.so.3 /usr/bin/lockfile-create
usage: lockfile-create [--use-pid] [--retry retry-count] [--lock-name] file
Proper ELF interpreter on armhf is /lib/ld-linux-armhf.so.3.
Best regards,
Dmitri Gribenko
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 CPU cores)
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lockfile-progs depends on:
ii libc6 2.13-30
ii liblockfile1 1.09-3
lockfile-progs recommends no packages.
lockfile-progs suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
