Re: Updating lintian.debian.org

[Niels Thykier <niels@thykier.net>]

On 2011-07-18 04:21, Russ Allbery wrote:
> Russ Allbery <rra@debian.org> writes:
> 
>> I just updated the version of Lintian on lintian.debian.org to 2.5.1 and
>> am doing a new full run, since there were a bunch of false positives
>> with the older version that we should clear out.  This will take a
>> couple of days.
> 
> This is done and seems to have worked, but there were a ton of errors in
> the logs along the lines of:
> 
> warning: could not create the package entry in the lab
> warning: skipping check of binary package zendframework-resources
> warning: could not create the package entry in the lab
> warning: skipping check of binary package zendframework
> warning: could not create the package entry in the lab
> warning: skipping check of binary package zendframework-bin
> 
> while processing the source packages.  I'm not sure what's up with that.
> 


That looks weird indeed.  The code in question would be
Lab::Package::create_entry, but for a binary package at that time, it
basically a mkdir + a symlink.  My best bet is that it got the wrong
info somehow.
  However I cannot really tell what it is, since it works for a lot of
packages.  It does not appear to be epoch or weird binary versions
compared to the source package.  java-common is a prime example at that
and there are no issues there.

I noticed some of the source packages fail due to missing keys[KEYS].

I digged out the names of the source packages for which at least one
binary failed: missidentify, nexuiz-data, ninix-aya, nodejs, openblas,
optgeo, ossim, oxygen-icons.

It does not seem to be "source name" == "binary package" either, but
according to grep the warning (could not create the package entry...)
appears 1707 times, so it is definitely a re-occurring problem.
  I do not suppose we got a pre 2.5.1 log? lintian.log and
lintian.log.old both appears to be the new one.

~Niels


[KEYS] fastx-toolkit, libdbusmenu, media-player-info