Re: Severity bump script

2019-12-08 Thread Sandro Tosi
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

2019-12-05 Thread Paul Gevers
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

2019-12-03 Thread Matthias Klose
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

Re: Severity bump script

2019-12-03 Thread Ondrej Novy
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

Re: Severity bump script

2019-12-02 Thread Mattia Rizzolo
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

2019-12-02 Thread Sandro Tosi
> 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

Re: Severity bump script

2019-12-02 Thread Paul Gevers
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

Re: Severity bump script

2019-12-02 Thread Sandro Tosi
> > 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

Re: Severity bump script

2019-12-02 Thread Ondrej Novy
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. >

Re: Severity bump script

2019-12-02 Thread Paul Gevers
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

2019-12-02 Thread Paul Gevers
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

Re: Severity bump script

2019-12-01 Thread Sandro Tosi
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 directly to me (i may be the mail address sending those

Re: Severity bump script

2019-11-28 Thread Ondrej Novy
Hi, čt 28. 11. 2019 v 19:07 odesílatel Sandro Tosi napsal: > this is live now, with the following header: > cool, thanks again! -- Best regards Ondřej Nový

Re: Severity bump script

2019-11-28 Thread Sandro Tosi
> I think we should use something simple/short like this: > > --cut-- > Raising severity of Python 2 removal bugs, for details see: > https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > --cut-- this is live now, with the following header: # Part of the effort for the removal

Re: Severity bump script

2019-11-28 Thread Ondrej Novy
Hi, čt 28. 11. 2019 v 4:12 odesílatel Sandro Tosi napsal: > i'm not sure we can: in > https://lists.debian.org/debian-python/2019/10/msg00096.html you say > "We need to prepare draft of RC-bumper email", is this draft ready? > ah, you are right. > add the description to the header (as

Re: Severity bump script

2019-11-27 Thread Sandro Tosi
On Wed, Nov 27, 2019 at 2:16 PM Ondrej Novy wrote: > > Hi, > > pá 22. 11. 2019 v 22:22 odesílatel Sandro Tosi napsal: >> >> I've removed bugs that are marked as blocked by; we're now down to 487 >> unique severity raies > > > cool. Checked and imho it works fine now. So I guess we can run it.

Re: Severity bump script

2019-11-27 Thread Ondrej Novy
Hi, pá 22. 11. 2019 v 22:22 odesílatel Sandro Tosi napsal: > I've removed bugs that are marked as blocked by; we're now down to 487 > unique severity raies > cool. Checked and imho it works fine now. So I guess we can run it. Thanks. -- Best regards Ondřej Nový

Re: Severity bump script

2019-11-22 Thread Sandro Tosi
On Fri, Nov 22, 2019 at 3:23 AM Ondrej Novy wrote: > > Hi Sandro, > > thanks for first version. I randomly checked few lines and found this: > > # libufo0 is an application and has low popcon (25 < 300) > severity 938743 serious > # libufo-bin is an application and has low popcon (4 < 300) >

Re: Severity bump script

2019-11-22 Thread Ondrej Novy
Hi Sandro, thanks for first version. I randomly checked few lines and found this: # libufo0 is an application and has low popcon (25 < 300) severity 938743 serious # libufo-bin is an application and has low popcon (4 < 300) severity 938743 serious # libufo-dev is an application and has low

Re: Severity bump script

2019-11-15 Thread Sandro Tosi
> I see that the script considers some -doc packages as modules. good point; fixed, but that only brings down the unique severity bumps to 688 > I can’t tell if we should remove them, but maybe the description could > be updated? Like “python-foo-doc is a documentation package has 0 external >

Re: Severity bump script

2019-11-15 Thread Dmitry Shachnev
Hi Sandro! On Thu, Nov 14, 2019 at 07:13:49PM -0500, Sandro Tosi wrote: > where is the first draft: > http://sandrotosi.me/debian/py2removal/would_raise_to_rc.txt (it will > be updated every time the script runs) > > there are 703 unique severity bumps roughly half of the pending bugs. > please

Re: Severity bump script

2019-11-14 Thread Sandro Tosi
On Mon, Nov 11, 2019 at 1:29 AM Ondrej Novy wrote: > > Hi Sandro, > > -- Forwarded message - > > We are going to raise the severity of the py2removal bugs to "serious" in > > several steps. In the > > first phase we are going to raise severity of the py2removal bugs for > > all

Re: Severity bump script

2019-11-11 Thread Sandro Tosi
On Mon, Nov 11, 2019 at 1:29 AM Ondrej Novy wrote: > > Hi Sandro, > > -- Forwarded message - > > We are going to raise the severity of the py2removal bugs to "serious" in > > several steps. In the > > first phase we are going to raise severity of the py2removal bugs for > > all