Bug#759403: lintian: Please publish machine-readable report for all packages

2019-08-03 Thread Chris Lamb
Hi intri, > … so I'll have to loop over this large list of packages, query UDD > with smaller subsets at a time, and somehow merge the results (that > can have duplicates since the input in a list of binary packages). Querying UDD directly via SQL is almost trivial to the point that it genuinely

Bug#759403: lintian: Please publish machine-readable report for all packages

2019-08-03 Thread intrigeri
Control: tag -1 - moreinfo Hi Chris! Chris Lamb: >> on the pkg-perl team, we would like to track the hardening status of >> our packages (same goes in Tails, to track the hardening status of the >> packages we ship). >> >> The easiest way for us would possibly be to retrieve data about all >> pa

Bug#759403: lintian: Please publish machine-readable report for all packages

2019-08-03 Thread Chris Lamb
tags 759403 + moreinfo thanks Hi Intrigeri, > on the pkg-perl team, we would like to track the hardening status of > our packages (same goes in Tails, to track the hardening status of the > packages we ship). > > The easiest way for us would possibly be to retrieve data about all > packages from

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-05 Thread Niels Thykier
intrigeri: > Niels Thykier wrote (05 Jul 2016 20:21:03 GMT) : >> Re: the memory usage; it may make sense to do the report as multiple >> "documents" (e.g. one per source package or something). > >> It would allow both generator and consumers to process it more >> efficiently by processing a single

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-05 Thread intrigeri
Niels Thykier wrote (05 Jul 2016 20:21:03 GMT) : > Re: the memory usage; it may make sense to do the report as multiple > "documents" (e.g. one per source package or something). > It would allow both generator and consumers to process it more > efficiently by processing a single source at the time

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-05 Thread Niels Thykier
intrigeri: > Hi, > > intrigeri wrote (05 Jul 2016 11:50:03 GMT) : >> Also, before we settle on this output format, I would like to quickly >> validate it by drafting code for the use case I had in mind for that >> machine-readable report. > > I drafted that code in Python 3 and then in Perl (sinc

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-05 Thread intrigeri
Hi, intrigeri wrote (05 Jul 2016 11:50:03 GMT) : > Also, before we settle on this output format, I would like to quickly > validate it by drafting code for the use case I had in mind for that > machine-readable report. I drafted that code in Python 3 and then in Perl (since the Python 3 version n

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-05 Thread intrigeri
Hi, Niels Thykier wrote (02 Jul 2016 17:47:46 GMT) : > Sure, I don't mind that being fixed later. Though we should probably > fix it relatively soon as it is relevant / less confusing than having > every tag once for every architecture. Fully agreed. > But again, you are very welcome to start w

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-02 Thread Niels Thykier
intrigeri: > Hi, > > [...] > I have a working PoC locally for listing $SOURCE/$VERSION and the > corresponding source package tags. > Excellent. :) > But regarding binaries & udebs, I have a problem. It looks like > parse_lintian_log loses the architecture information along the way: > e.g. in $

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-07-02 Thread intrigeri
Hi, Niels Thykier wrote (27 Aug 2014 05:06:11 GMT) : > I am personally considering whether we should have it in one file. > Maybe something like: > "$SOURCE/$VERSION": > maintainer: ... > ... > binaries: > - "$BINARY1/$VERSION1/$ARCH" > tags: > - $TAG_NAME: >

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-05-09 Thread intrigeri
Niels Thykier wrote (22 Jan 2016 19:42:12 GMT) : > I believe it is has been easier to hack on html_reports now, Confirmed, thanks to your helpful hints I could build reports locally! > in case you are still interested in working on this. I am. Now, we'll see if/when I find time to actually get t

Bug#759403: lintian: Please publish machine-readable report for all packages

2016-01-22 Thread Niels Thykier
On Wed, 27 Aug 2014 07:06:11 +0200 Niels Thykier wrote: > On 2014-08-27 02:34, intrig...@debian.org wrote: > > Package: lintian > > Version: 2.5.25 > > Severity: wishlist > > > > Hi, > > > > Hi, > Hi, I believe it is has been easier to hack on html_reports now, in case you are still intereste

Bug#759403: lintian: Please publish machine-readable report for all packages

2014-08-26 Thread Niels Thykier
On 2014-08-27 02:34, intrig...@debian.org wrote: > Package: lintian > Version: 2.5.25 > Severity: wishlist > > Hi, > Hi, > on the pkg-perl team, we would like to track the hardening status of > our packages (same goes in Tails, to track the hardening status of the > packages we ship). > > The

Bug#759403: lintian: Please publish machine-readable report for all packages

2014-08-26 Thread intrigeri
Package: lintian Version: 2.5.25 Severity: wishlist Hi, on the pkg-perl team, we would like to track the hardening status of our packages (same goes in Tails, to track the hardening status of the packages we ship). The easiest way for us would possibly be to retrieve data about all packages from