Hi Doug, > This is caused by library having executable bits set, which is how the > pie executable vs shared object check in file works.
Oh..! Hm, okay, just pondering what this means for Lintian. We seem to be doing this deliberately in the testsuite: https://salsa.debian.org/lintian/lintian/blob/master/t/tests/legacy-libbaz/debian/debian/rules#L102-103 Now, if this is actually checking for something that could appear in the real world we can't just turn this off here. Thus, should we also be looking for "pie executable" every time we previously looked for "shared object" in $fileinfo? That, also, seems a little risky. FYI for confirmation of the executable bits: $ file -v file-5.33 magic file from /etc/magic:/usr/share/misc/magic $ chmod +x libbaz2.so.1.0.3b $ file libbaz2.so.1.0.3b libbaz2.so.1.0.3b: ELF 64-bit LSB pie executable x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=dfe311f4305ebf88da3b18fe8408460f6513f440, with debug_info, not stripped $ chmod -x libbaz2.so.1.0.3b $ file libbaz2.so.1.0.3b libbaz2.so.1.0.3b: ELF 64-bit LSB shared object x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=dfe311f4305ebf88da3b18fe8408460f6513f440, with debug_info, not stripped Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
