Bug#655977: marked as done (queue-viewer: lintian support)
Your message dated Sun, 13 Nov 2016 11:47:35 +0000
with message-id <1479037655.2601.49.camel@adam-barratt.org.uk>
and subject line Re: Bug#655977: queue-viewer: lintian support
has caused the Debian Bug report #655977,
regarding queue-viewer: lintian support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
655977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655977
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: wishlist
User: release.debian.org@packages.debian.org
Usertags: tools
It would be useful if queue-viewer could run lintian on uploaded
source / binary packages.
For the purpose of highlighting issues on the queue report, a diff would
need to be generated against the package version in the base suite (or
maybe the overlay if there's already a package there?) and only changes
displayed.
Adam
--- End Message ---
--- Begin Message ---
On Sat, 2016-11-12 at 18:12 +0000, Adam D. Barratt wrote:
> Control: tags -1 + pending
>
> On Sun, 2012-01-15 at 16:16 +0000, Adam D. Barratt wrote:
> > It would be useful if queue-viewer could run lintian on uploaded
> > source / binary packages.
> >
> > For the purpose of highlighting issues on the queue report, a diff would
> > need to be generated against the package version in the base suite (or
> > maybe the overlay if there's already a package there?) and only changes
> > displayed.
>
> For the benefit of the log, and those not following in #-release, I've
> deployed some support for this. Reports for all packages currently in
> p-u and stable-new are currently being generated.
>
> I'll close the bug once that's done and I've checked the output looks
> reasonable (my test run earlier today took several hours end-to-end).
That all seems to be working fine.
Adam
--- End Message ---
Reply to: