Your message dated Wed, 27 Feb 2013 18:28:59 -0600
with message-id <[email protected]>
and subject line Re: Bug#670770: lockfile-progs: Wrong ELF interpreter on armhf
has caused the Debian Bug report #670770,
regarding lockfile-progs: Wrong ELF interpreter on armhf
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 [email protected]
immediately.)


-- 
670770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670770
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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



--- End Message ---
--- Begin Message ---
Rob Browning <[email protected]> writes:

> Dmitri Gribenko <[email protected]> writes:
>
>> 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.
>
> Perhaps the cause:
>
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670597
>

At this point, I'm going to assume that was the case, but feel free to
reopen the bug if it turns out I'm mistaken.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

--- End Message ---

Reply via email to