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

Bug#1016074: marked as done (UDD/lintian: please add search option to filter by lintian tags)



Your message dated Thu, 28 Jul 2022 21:46:57 +0200
with message-id <YuLnsYJn5V6bTqc7@xanadu.blop.info>
and subject line Re: Bug#1016074: UDD/lintian: please add search option to filter by lintian tags
has caused the Debian Bug report #1016074,
regarding UDD/lintian: please add search option to filter by lintian tags
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.)


-- 
1016074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016074
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
User: qa.debian.org@packages.debian.org
Usertags: udd
Severity: wishlist

Hi,

It would be really nice if the lintian web page for UDD let you filter
by lintian tags.

This way, it would be easier to do QA work on some things that are
flagged by lintian :)

Cheers, and thanks for running lintian!

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

--- End Message ---
--- Begin Message ---
Hi,

On 26/07/22 at 22:34 +0200, Lucas Nussbaum wrote:
> Hi,
> 
> On 26/07/22 at 11:11 -0400, Louis-Philippe Véronneau wrote:
> > Package: qa.debian.org
> > User: qa.debian.org@packages.debian.org
> > Usertags: udd
> > Severity: wishlist
> > 
> > Hi,
> > 
> > It would be really nice if the lintian web page for UDD let you filter
> > by lintian tags.
> > 
> > This way, it would be easier to do QA work on some things that are
> > flagged by lintian :)
> 
> So I thought about that, and there are several possible workarounds:
> 
> 1/ add some client-side filtering of the results table using javascript
> (I would welcome a patch for that, my js is rusty)

I implemented this...

And then I changed my mind and also implemented server-side filtering,
because client-side filtering is too slow for large teams when looking
at "classification" tags.

Lucas

--- End Message ---

Reply to: