[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Non-HF binaries in some Grip ARMHF debs

On Fri, 14 Jun 2013 13:04:49 +0100
Wookey <wookey@wookware.org> wrote:
> +++ Paul Whittaker [2013-06-14 18:41 +1000]:
> > 
> > It's the runtime linker name.  They're expecting /lib/ld-linux.so.3
> > instead of /lib/ld-linux-armhf.so.3, 
> OK. That is indeed packages left over from when armhf was started in
> 'ports'. The linker path was changed later to align with other
> distros. Looks like some packages managed to avoid being rebuilt.
> binNMUs should fix that. (can we do grip-only binNMUs Neil? I really
> should get up to date with how the mechanics on all this work these
> days).

Grip can't do binNMU's (we don't build stuff) but what I can do is
remove and insert because the main problem is that Emdebian Grip had a
package from ports which had exactly the same version string as the one
pushed to Debian. When the Debian package was downloaded, it matched an
existing binary so couldn't replace it.

I'll need a way of scanning for this problem inside the packages. Is
there a way of identifying the problem? I can get some hints from
objdump -p in looking for:
  required from ld-linux-armhf.so.3:
inside the Version References section.

Do you know if this is sufficiently reliable that I don't get flooded
with false positives?

There isn't time to do a mass rebuild of armhf before the point release
this weekend.


Neil Williams

Attachment: pgp_N5IHqHqpX.pgp
Description: PGP signature

Reply to: