> i have a semi-working script that produced ~400 package depending on
> py2 packages with missing py2removal bugs, i'll try to finalize it in
> the coming days and submit those bugs when done
i found approximately 140 more packages that depends on python/cython
and dont have a py2removal bug;
Hi,
po 28. 10. 2019 v 10:56 odesílatel Simon McVittie napsal:
> The maintainer of a leaf package can do this in a few minutes at any
> time, but library packages with many reverse-dependencies (for example
> dbus-python) don't really have that option, so I hope using autorm for
> library
On Fri, 25 Oct 2019 at 12:38:11 +0200, Ondrej Novy wrote:
> this is not how autorm works. You can't remove from testing only one of two
> binary package from same source package. You are removing package as a whole.
>
> But maintainer can anytime fix that bug by removing py2 binary from source
>
Hi,
pá 25. 10. 2019 v 9:09 odesílatel Rebecca N. Palmer
napsal:
> Not the whole source package, but we do want to remove the py2 binary.
> Maybe there should be two versions of the email, with the one for py2/3
> packages saying 'NMU' instead of 'removal'?
>
this is not how autorm works. You
Hi,
pá 25. 10. 2019 v 3:30 odesílatel Sandro Tosi napsal:
> do we really want to remove from testing (and subsequently from
> debian, as mentioned below) if it both has a py2 and a py3k package?
> should we limit this to py2-ONLY packages?
>
yes and no. If maintainer wants to keep package in
Sandro Tosi wrote:
do we really want to remove from testing (and subsequently from
debian, as mentioned below) if it both has a py2 and a py3k package?
should we limit this to py2-ONLY packages?
Not the whole source package, but we do want to remove the py2 binary.
Maybe there should be two
> notes from this meeting
> (https://gobby.debian.org/export/Teams/Python/Py2Removal):
small additional note: the py2removal tracker script now ignores
Suggests and wont mark them as rdeps
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
On Thu, Oct 24, 2019 at 4:09 PM Ondrej Novy wrote:
> We want to bump all bugs to RC bugs, if they are:
Was there anyone from the RT that ack'd this? Paul is here and i guess
he can do that now: there could be hundreds of new RC bugs in a blink.
> * leaf package
> * with py2 binary
do we really
Hi,
notes from this meeting (
https://gobby.debian.org/export/Teams/Python/Py2Removal):
We want to bump all bugs to RC bugs, if they are:
* leaf package
* with py2 binary
* bug is not marked as py2keep
* all modules and low popcon apps (< 300)
If package will be removed from testing (auto-rm),
> i have a semi-working script that produced ~400 package depending on
> py2 packages with missing py2removal bugs, i'll try to finalize it in
> the coming days and submit those bugs when done
here's the list:
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt in
format
all of
Dear all,
On 22-10-2019 17:04, Matthias Klose wrote:
> He suggested to make the removal plan more
> concrete and having a timeline.
To be more precise on what I meant, I'm talking here about *every*
package that wants to drop a Python 2 binary package, discuss (and
ideally agree on, but I
On Tue, Oct 22, 2019 at 11:05 AM Matthias Klose wrote:
>
> Paul Gevers from the release team pointed out that the Python2 removal is
> causing some uninstall-ability issues in testing because some packages
> apparently are removed too early, but never the less are migrating to testing.
in a hope
Paul Gevers from the release team pointed out that the Python2 removal is
causing some uninstall-ability issues in testing because some packages
apparently are removed too early, but never the less are migrating to testing.
He suggested to make the removal plan more concrete and having a
13 matches
Mail list logo
