Alejandro Colomar wrote:
> alx@debian:~/src/alx/liba2i/contrib$ file liba2i*.a
> liba2i.a: current ar archive
> liba2i_ranlibbed.a: current ar archive
Now that's puzzling. Okay, so we might be in danger of actually
debugging why these are identified as 'data' on my system (rather than
fixing the subsequent traceback), but this is enough of an eyebrow-raiser
to work out what is going on.
As in, I'm also running the same version as file as you:
$ dpkg -l file | tail -n1
ii file 1:5.45-3 amd64 Recognize the type […]
Okay, before we do anything else, just so we know we are 100% dealing
with the same files (it has happened!), here is what I'm attempting to
reproduce with:
$ sha1sum liba2i.a liba2i_ranlibbed.a
677d551cf0db663ff7a269133a4e7b297ef57f3e liba2i.a
0c9ac6a9720a69f595510cca27a1c266b2ba3172 liba2i_ranlibbed.a
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
