Bug#521257: Use of uninitialized value in bitwise or (|) at /usr/share/lintian/lib/Lintian/Command.pm line 308.

[Raphael Geissert <atomo64+debian@gmail.com>]

Hi,

Michael Tautschnig wrote:

> Package: lintian
> Version: 2.2.8
> 
> While checking the clamav packages (you can grab these from
> http://people.debian.org/~mt/clamav/) a few warnings where shown; I've
> repeated the process using -d, which results in the following output:
> 
[...]
> N: Waiting for jobs from order 1 ...
> internal error: command failed with error code 123
> warning: collect info file-info about package clamav failed
> warning: skipping check of source package clamav
> N: ----
> N: Processing binary package clamav (version 0.95+dfsg-1) ...
> Use of uninitialized value in bitwise or (|) at
> /usr/share/lintian/lib/Lintian/Command.pm line 308. Use of uninitialized
> value in bitwise or (|) at /usr/share/lintian/lib/Lintian/Command.pm line
> 308. Use of uninitialized value in bitwise or (|) at
> /usr/share/lintian/lib/Lintian/Command.pm line 308. Use of uninitialized
> value in bitwise or (|) at /usr/share/lintian/lib/Lintian/Command.pm line
> 308. N: Base directory in lab: /tmp/i27fWIhHW7/binary/clamav
> 

I'm unable to reproduce it, but the error in Command.pm can be fixed with:
diff --git a/lib/Lintian/Command.pm b/lib/Lintian/Command.pm
index 0292fea..5ba58ed 100644
--- a/lib/Lintian/Command.pm
+++ b/lib/Lintian/Command.pm
@@ -303,7 +303,7 @@ all the executions of kill_kill.
 =cut

 sub kill {
-    my $status;
+    my $status = 0;
     while (my $opts = shift @_) {
        $status |= kill_kill($opts->{'harness'}, grace => 2);
     }


Could you please run lintian with --keep-lab, and in the generated lab (you
can manually specify one with --lab, or use -d to see where it was created)
and attach the path/to/lab/source/clamav/index file?

> [...] (no further errors)
> 
> I think the "commmand failed with error code 123" issue has been reported
> before already, but the uninitialized value in line 308 seems new.

The "command failed..." error was supposed to be fixed in 2.2.8, but looks
like something is missing.

Cheers,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net