Re: Severity bump script

there seems to be disagreement on how to proceed, so for the time being i suspended the severity bump part of the py2removal tracking script. let me know when everybody agrees on a solution, and what that solution is, and i'll code it and re-enable. regards, Sandro On Thu, Dec 5, 2019 at 6:07 AM

Re: Severity bump script

Hi, On 03-12-2019 13:19, Matthias Klose wrote: > It's unfortunate that issues for some packages only get attention when the > severity of an issue is raised. Following your proposal means that the issue > is > probably ignored forever, and you don't propose a better way going forward, > just >

Re: Severity bump script

On 02.12.19 20:28, Paul Gevers wrote: > Hi all, > > On 01-12-2019 22:45, Sandro Tosi wrote: >> Paul, this is the thread i was talking about. >> >> you were copied in the original email: >> https://lists.debian.org/debian-python/2019/10/msg00098.html >> >> if there is something the RT wants to disc

Re: Severity bump script

Hi, po 2. 12. 2019 v 20:36 odesílatel Paul Gevers napsal: > #942999 and #936537 > ah right. I think this is correct. There is nothing else "in Python 2 removal process" to do on "someone else" packages. Work needs to be done in these packages so raise severity here to unblock other bugs and con

Re: Severity bump script

On Mon, 2 Dec 2019, 10:25 pm Paul Gevers, wrote: > Hi, > > On 02-12-2019 22:15, Sandro Tosi wrote: > > the blocks are only between py2removal packages, so if a package > > un-related to the py2removal effort > > depend/recomments/b-deps/autotest-triggers a py2removal *application*, > that > > is

Re: Severity bump script

> You'll fix that, right? Because why would the tree stop at Python? A > leaf package is a package without Depends/Build-Depends in Debian. (I > appreciate it very much that you consider Recommends and > autopkgtest-triggers as well). so the revised logic should be: * it's an app (package name do

Re: Severity bump script

Hi, On 02-12-2019 22:15, Sandro Tosi wrote: > the blocks are only between py2removal packages, so if a package > un-related to the py2removal effort > depend/recomments/b-deps/autotest-triggers a py2removal *application*, that > is still considered a leaf package You'll fix that, right? Because w

Re: Severity bump script

> > huh? We are not bumping any "blocked" bugs. > > Depends/Build-Depends/Recommends/autopkgtests usage marks bug as > > blocked. Any example of "wrong definition" please? > > #942999 and #936537 the blocks are only between py2removal packages, so if a package un-related to the py2removal effort d

Re: Severity bump script

Hi, po 2. 12. 2019 v 20:28 odesílatel Paul Gevers napsal: > I understand the drive to push for Python 2 removal and sympathize with > it. The issue I had yesterday with the process is that "leaf" was > wrongly defined, it was looking at Depends, instead of also including > Build-Depends. > huh?

Re: Severity bump script

Hi Ondrej, On 02-12-2019 20:33, Ondrej Novy wrote: > Hi, > > po 2. 12. 2019 v 20:28 odesílatel Paul Gevers > napsal: > > I understand the drive to push for Python 2 removal and sympathize with > it. The issue I had yesterday with the process is that "leaf" was

Re: Severity bump script

Hi all, On 01-12-2019 22:45, Sandro Tosi wrote: > Paul, this is the thread i was talking about. > > you were copied in the original email: > https://lists.debian.org/debian-python/2019/10/msg00098.html > > if there is something the RT wants to discuss about this effort, > please do so here, not