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

Bug#723037: marked as done (UDD/bugs.cgi: please add an "older than oldstable" release selection)

Your message dated Sun, 3 Jul 2016 22:50:06 +0200
with message-id <20160703205006.GA23907@xanadu.blop.info>
and subject line Re: Bug#723037: [qa.debian.org] Please add an "older than oldstable" release selection
has caused the Debian Bug report #723037,
regarding UDD/bugs.cgi: please add an "older than oldstable" release selection
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.)


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

--- Please enter the report below this line. ---

Hi!
For bug triaging it would be useful to be able to select older bugs,
i.e. bugs affecting releases before oldstable. It may be too much work
to add that just for this purpose, please let me know :)

It's also a possibility to add it to the backend but not the web
interface, as it's not useful for everybody. If you prefer that, I can
find people to run the UDD request for me.

 Solveig

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

On 15/09/13 at 19:14 +0200, Solveig wrote:
> Package: qa.debian.org
> Severity: wishlist
> User: qa.debian.org@packages.debian.org
> Usertags: udd
> 
> --- Please enter the report below this line. ---
> 
> Hi!
> For bug triaging it would be useful to be able to select older bugs,
> i.e. bugs affecting releases before oldstable. It may be too much work
> to add that just for this purpose, please let me know :)
> 
> It's also a possibility to add it to the backend but not the web
> interface, as it's not useful for everybody. If you prefer that, I can
> find people to run the UDD request for me.

UDD gets bugs presence information from the BTS. And the BTS gets it
from version-tracking. AFAIK, the BTS doesn't do version-tracking for
archived releases, so there's no real way to get exactly those bugs.

The closest you could get is to look at open bugs about existing
packages, that are known not to affect one of
(oldstable,stable,testing,unstable,experimental). This query can serve
as a basis:

select id, bugs.package, bugs.source, severity, title, last_modified, affects_stable, affects_testing, affects_unstable, affects_experimental from bugs 
where id not in (select id from bugs_rt_affects_oldstable)
and id not in (select id from bugs_rt_affects_stable)
and id not in (select id from bugs_rt_affects_testing)
and id not in (select id from bugs_rt_affects_unstable)
and not affects_stable
and not affects_oldstable
and not affects_testing
and not affects_unstable
and not affects_experimental
and not (id in (select id from bugs_merged_with where id > merged_with)) 
and not (id not in (select id from bugs_packages, sources where bugs_packages.source = sources.source and release='stretch'))
AND (severity >= 'serious')
and not (status = 'done')
order by id asc

I'm closing this bug. I really don't see another path forward.

Lucas

--- End Message ---
Reply to: