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 still considered a leaf package
>
> 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.


Because the python2 removal is about python2.  If you depend on a python2
package then the dependant application needs to likewise be dropped or
updated, but it also is at the same time somewhat out of scope from "us".

So it's either file py2removal bugs also against packages that don't depend
on python, but just use an application that happens to use python2, or the
current status quo.
That's my take at least.

Also, I am one of those that think we should be much more forceful, and the
current situation looks just fine for me, so I might be biased.


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 doesnt start with 'python-' or end with -'doc')
* it has low popcorn (< 300)
* (NEW) it has "real" rdep = 0 (so the number of dependencies from
packages not from the same source pkg are 0)

is that correct or should it be something else?


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



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 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).

Paul



signature.asc
Description: OpenPGP digital signature


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
depend/recomments/b-deps/autotest-triggers a py2removal *application*, that
is still considered a leaf package and will get its severity
raised (cfr 
https://github.com/sandrotosi/debian-tools/blob/master/py2rm_progress.py#L544-L546
); it doesnt happen with modules are we check the "real" rdeps for
those


--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



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.
>

huh? We are not bumping any "blocked" bugs.
Depends/Build-Depends/Recommends/autopkgtests usage marks bug as blocked.
Any example of "wrong definition" please?

-- 
Best regards
 Ondřej Nový


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
> wrongly defined, it was looking at Depends, instead of also including
> Build-Depends.
> 
> 
> 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

Paul



signature.asc
Description: OpenPGP digital signature


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 directly to me (i may be the mail address
> sending those control commands, but the decision was taken here).

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.

I don't want to stand in the way of Python 2 removal, but as I said
before, pulling packages out from underneath maintainers isn't pretty so
needs to be done with proper notifications and care. An RC bug to ones
own package is acceptable in my opinion as it is a clear discussion
forum, and can be (temporarily) down-graded while the discussion is
ongoing. Being notified about some other package that I not even need
directly but is going to pull "my" package out of testing isn't a nice
experience and should be avoided. Yes, that slows down the process, but
there are people, emotions and all those irrational things involved.

Paul



signature.asc
Description: OpenPGP digital signature