[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#960154: UDD table no longer populated



clone 960154 -1
retitle 960154 lintian: please provide a stable, parsable output
reassign -1 qa.debian.org
user qa.debian.org@packages.debian.org
usertags -1 udd
block -1 by 960154
retitle -1 udd.debian.org: change the lintian importer to use the new export file
thanks

On Sat, May 09, 2020 at 11:37:52PM +0000, Jelmer Vernooij wrote:
> Not sure whether to file this against UDD or lintian or detagtive; filing it
> against lintian since it changed more recently and I suspect that's related.

It was caused by a change in lintian, but it will have to be fixed in
both lintian and udd.

> For a while now, the UDD tables for lintian have been empty. They were
> previously populated with lintian data.

This was discussed recently in #-qa.
The frontend rewrite lechner did, completely removed the logs.gz that
was used by udd (and not only udd, I fear…)

I believe the first step is going to have lintian decide on a nice
machine-parsable (text!) format and publish that; then udd will adopt
its importer.


(PS, lechner: I went looking in lindsay to see if there was already a
replacement for the logs.gz file, and I noticed that the files under
/srv/lintian.debian.org/ are all with mixed ownership lintian:lintian
and lechner:lintian.... that might not be a issue right now since you
are the only one working on that part of lintian, but it's not quite
nice to any other team member in the future, even if the umask seems to
allow all team members to edit those files; I recommend you take on the
habit to deploy that stuff entirely under the role account.)


-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: