[
Maintainer of the file package here - feel free to Cc me early, this
might or might not ease things.
]
Chris Lamb wrote...
> [adding elbrus@debian.org to CC]
>
> Chris Lamb wrote:
>
> > > This is caused by library having executable bits set, which is how the
> > > pie executable vs shared object check in file works.
> […]
> > FYI for confirmation of the executable bits:
>
> The more I think about it, the more I think this is a misleading
> and non-intuitive misfeature of file.
This was indeed added upstream:
->16 leshort 3 shared object,
+>16 leshort 3 ${x?pie executable:shared object}
<https://github.com/file/file/commit/6876ebadcdf27224b3ffa9dfa4343127aa97c9b2>
This exansion feature ${x?(...):(...)} was added just in the preceeding
commit. So the executable bit of the file indeed affects the detection
now. While personally I'm not too happy about that, I think it was the
worse idea to work around this in file permanentely by reverting that
change.
> Any thoughts before I essentially re-assign this?
Rather somehow deal with it?
Christoph
Attachment:
signature.asc
Description: PGP signature