Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Norbert Preining
Hi Mo, On Tue, 12 Nov 2019, Mo Zhou wrote: > How many users still use these unmaintained scripts? Could you please > provide us a reference/estimated popcon so we can better understand the > situation of texlive in terms of py2rm. Popcon does not help, since these scripts are part of a huge colle

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Mo Zhou
On Tue, Nov 12, 2019 at 10:07:26AM +0900, Norbert Preining wrote: > Yes, we have a lot of python scripts, and some have been written more > than 10 years ago, and there is no maintainer anymore. > ... > And *we* at the TeX side prefer not to simply throw out old stuff, see > above. How many users

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Norbert Preining
Hi Matthias, On Mon, 11 Nov 2019, Matthias Klose wrote: > sure, and when everybody is doing that, we end up with Python2 in bullseye+2 > as well. Python3 is around for 10+ years now... Well, the whole py2/py3 mess shouldn't have happened at all, but this is not any of our faults, but purely Pytho

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Norbert Preining
Hi Ondrey, hi all, thanks to you (and all the others) for answers. > It's team work, I "only" sent that email :). It looks like others already Yes, in this sense with "you" I meant the Python Team and everyone working on it. > time line=now. 1.5 year is really short period for doing so much wor

Re: Automated removal of RC buggy packages

2019-11-11 Thread Sam Hartman
> "Matthias" == Matthias Klose writes: Matthias> why do you even consider such uploads suitable for Matthias> unstable? That's something which should go to Matthias> experimental. And I would like to see some automatic Matthias> demotion from unstable to experimental for pac

Re: Automated removal of RC buggy packages

2019-11-11 Thread Matthias Klose
On 12.11.19 00:00, Sam Hartman wrote: "Moritz" == Moritz Mühlenhoff writes: Moritz> Scott Kitterman schrieb: >> One maintainer doesn't get to block the removal of an entire >> stack like Qt4. I think there's a reasonable point of discussion >> about when RoQA is appropria

Re: Automated removal of RC buggy packages

2019-11-11 Thread Moritz Mühlenhoff
On Mon, Nov 11, 2019 at 06:00:18PM -0500, Sam Hartman wrote: > Moritz> We should even work towards automating this further; if a > Moritz> package is RC-buggy for longer than say a year (with some > Moritz> select exceptions) it should just get auto-removed from the > Moritz> archiv

Automated removal of RC buggy packages

2019-11-11 Thread Sam Hartman
> "Moritz" == Moritz Mühlenhoff writes: Moritz> Scott Kitterman schrieb: >> One maintainer doesn't get to block the removal of an entire >> stack like Qt4. I think there's a reasonable point of discussion >> about when RoQA is appropriate, but there comes a time when stuff

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Moritz Mühlenhoff
Scott Kitterman schrieb: > One maintainer doesn't get to block the removal of an entire stack like Qt4. > I think there's a reasonable point of discussion about when RoQA is > appropriate, but there comes a time when stuff just has to go. > That doesn't make it a free for all, but for old, unsuppo

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Ondřej Surý
Sorry for top post, I am just on my phone. Just my two cents - the RoQA is a pretty standard thing when you deal with bigger transitions and there’s a lot of unmaintained packages. Been there couple of times, and it was nowhere near py2 removal magnitude. So, I just want to send huge thanks tow

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Ondrej Novy
Hi, po 11. 11. 2019 v 16:27 odesílatel Norbert Preining napsal: > thanks for your work on the Python2 removal. > It's team work, I "only" sent that email :). It looks like others already replied, but Could you please give a time line of how you are planning to proceed? > time line=now. 1.5 ye

Bug#944563: ITP: libb-cow-perl -- additional B helpers to check COW status

2019-11-11 Thread gregor herrmann
Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libb-cow-perl Version : 0.001 Upstream Author : Nicolas R. * URL : https://metacpan.org/release/B-COW * License :

Re: please avoid writing useless/annoying stuff in debian/gbp.conf

2019-11-11 Thread Russ Allbery
"Theodore Y. Ts'o" writes: > Yes, and that's why I use debian/master instead of debian/buster or > debian/bullseye. :-) > When I do create debian/buster (once it became the stable branch), the > first thing I did after I branched off debian/buster from debian/master > was to edit debian/gbp.con

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Scott Kitterman
On November 11, 2019 3:10:32 PM UTC, Norbert Preining wrote: >Hi Ondřej, > >(please Cc, I am not subscribed to debian-devel) > >thanks for your work on the Python2 removal. > >On Mon, 11 Nov 2019, Ondřej Nový wrote: ... > >Furthermore, > >> We will also then file bug reports against ftp.debian

Re: please avoid writing useless/annoying stuff in debian/gbp.conf (was: source only upload with git-buildpackage)

2019-11-11 Thread Theodore Y. Ts'o
On Mon, Nov 11, 2019 at 08:58:42AM +0100, Thomas Goirand wrote: > >> Please, *never* do that. It's generally a very bad idea to write > >> anything to debian/gbp.conf. It's as if you were adding your text editor > >> preferences in the package. Instead, please prefer writing in ~/.gbp.conf. > > >

Bug#944543: ITP: erlang-unicode-util-compat -- unicode_util compatibility library for Erlang <= 20

2019-11-11 Thread Philipp Huebner
Package: wnpp Severity: wishlist Owner: Philipp Huebner * Package name: erlang-unicode-util-compat Version : 0.5.0 Upstream Author : Benoit Chesneau * URL : https://github.com/benoitc/unicode_util_compat * License : Apache-2.0 Programming Lang: Erlang Descr

Bug#944540: ITP: erlang-idna -- pure Erlang IDNA implementation that follows RFC 5891

2019-11-11 Thread Philipp Huebner
Package: wnpp Severity: wishlist Owner: Philipp Huebner * Package name: erlang-idna Version : 6.0.0 Upstream Author : Benoit Chesneau * URL : https://github.com/benoitc/erlang-idna * License : MIT Programming Lang: Erlang Description : pure Erlang IDNA

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Matthias Klose
On 11.11.19 16:10, Norbert Preining wrote: Hi Ondřej, (please Cc, I am not subscribed to debian-devel) thanks for your work on the Python2 removal. On Mon, 11 Nov 2019, Ondřej Nový wrote: We are going to raise the severity of the py2removal bugs to "serious" in several steps. In the ... Co

Bug#944539: ITP: ignition-cmake2 -- CMake modules to be used by the Ignition projects (v2)

2019-11-11 Thread Jose Luis Rivero
Package: wnpp Severity: wishlist Owner: Jose Luis Rivero * Package name: ignition-cmake2 Version : 2.1.1 Upstream Author : Open Source Robotics Foundation * URL : https://ignitionrobotics.org/libraries/cmake * License : Apache2 Programming Lang: CMake Descr

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Mattia Rizzolo
Hi, I'm going to answer, even if I'm not Ondrej :) On Tue, Nov 12, 2019 at 12:10:32AM +0900, Norbert Preining wrote: > On Mon, 11 Nov 2019, Ondřej Nový wrote: > > We are going to raise the severity of the py2removal bugs to "serious" > > in several steps. In the > ... > > Could you please give

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Norbert Preining
Hi Ondřej, (please Cc, I am not subscribed to debian-devel) thanks for your work on the Python2 removal. On Mon, 11 Nov 2019, Ondřej Nový wrote: > We are going to raise the severity of the py2removal bugs to "serious" > in several steps. In the ... Could you please give a time line of how you

Bug#944532: ITP: erlang-p1-acme -- ACME client library for Erlang

2019-11-11 Thread Philipp Huebner
Package: wnpp Severity: wishlist Owner: Philipp Huebner * Package name: erlang-p1-acme Version : 1.0.2 Upstream Author : ProcessOne * URL : https://github.com/processone/p1_acme * License : Apache-2.0 Programming Lang: Erlang Description : ACME client l

Re: please avoid writing useless/annoying stuff in debian/gbp.conf (was: source only upload with git-buildpackage)

2019-11-11 Thread Jeremy Bicha
On Mon, Nov 11, 2019 at 2:59 AM Thomas Goirand wrote: > On 11/11/19 1:02 AM, Theodore Y. Ts'o wrote: > > On Sun, Nov 10, 2019 at 11:20:45PM +0100, Thomas Goirand wrote: > >> > >> Please, *never* do that. It's generally a very bad idea to write > >> anything to debian/gbp.conf. It's as if you were

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Matthias Klose
On 11.11.19 10:33, Ondřej Nový wrote: Hi, We are aiming to remove Python 2 for the bullseye release, or at least remove as many Python 2 related packages as possible. Python 2 is discontinued upstream, but crucially, more and more providers of Python modules don't support Python 2 in either the