Bug#521257: Use of uninitialized value in bitwise or (|) at /usr/share/lintian/lib/Lintian/Command.pm line 308.
Russ Allbery wrote:
> Michael Tautschnig writes:
[...]
>
>> No sorry, that doesn't fix the problem, actually it seems it didn't
>> change anything.
>
> I think what we need to know is what file was attempting to process and
> failed. I'm trying to figure out the best way of doing that. Something
> is being passed to the file command that it doesn't like and that's
> causing it to exit with an error. If we can figure out what that thing
> is, we should be able to sort out what to do about it.
>
> Similar to Raphael, I can't duplicate the problem by running lintian on
> the files from the URL that you gave in the initial bug report. It works
> fine for me. Could you check to see what version of file that you have?
> If it produced any errors to stderr, that would be useful, but from your
> output it doesn't seem to be producing any error messages at all, just
> failing with a non-zero exit status. Which is very strange.
>
I just reproduced it on a clean sid chroot. file 5.00-1 is installed, and
the culprit are...
unpacked/test/.split/split.clam.ole.docaa: ERROR: Can't read SAT
unpacked/test/.split/split.clam.pptaa: ERROR: Can't read SAT
I reported this against file as #521772, and made sure the parsing of tar's
output is fine by comparing the output of what file-info pipes to file,
both outputs are byte-per-byte identical.
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
Reply to: