On Mon, Nov 11, 2019 at 1:29 AM Ondrej Novy <n...@ondrej.org> 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 leaf module packages and low popcon (< 300) application packages. > > Bugs marked with the "py2keep" user tag will not have their severity > > raised. > > is there any progress with script from your site please? First we need list > to check. Thanks a lot.
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 note there are duplicates in the list as data is per binary package, while bugs are on a source package basis. you can read the heuristic to determine if it's a module (https://github.com/sandrotosi/debian-tools/blob/master/py2rm_progress.py#L472) or and app (https://github.com/sandrotosi/debian-tools/blob/master/py2rm_progress.py#L475) in the links, they are pretty weak, is there a better way? all in all i think this is not the effect people were expecting: there are too many packages that would become RC-buggy; also the severity bump is done at the source package level, even if only a single binary in the pkg set matches the criteria (which, if you read the request above, it is what's wanted). Let me know what you think, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi