Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #11920

Re: Discussing next steps for the Python2 removal

From Paul Gevers <elbrus@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Discussing next steps for the Python2 removal
Date 2019-10-22 20:50 +0200
Message-ID <yU7od-3dZ-1@gated-at.bofh.it> (permalink)
References <yU3Xk-1fZ-19@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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 understand that that can be hard) the time line
with their reverse dependencies.

If this is done globally, fine, but please, give reverse dependencies
time to adapt. I'm already seeing quite some annoyance on the fact that
in several cases the ground is pulled away under one's package.

Yes, there's a bug in britney somewhere that allows the migration, we're
trying to find it.

Paul

For those that are curious, the britney output [1] shows at the end
binary packages in testing that are not build from source anymore but
are left in testing due to dependencies. Those that aren't in
libs/oldlibs shouldn't be there and are make their reverse dependencies
RC buggy. On top of that, Dose [2] shows packages that can't be build
from source in testing. There's quite some python2 packages listing as
causing that. Again, all those packages are RC buggy (often the bug
hasn't been filed yet).

[1] https://release.debian.org/britney/update_output.txt.gz
[2] https://qa.debian.org/dose/debcheck/src_testing_main/ (pick the
latest amd64 log, it should be empty except for cmucl)

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Discussing next steps for the Python2 removal Matthias Klose <doko@debian.org> - 2019-10-22 17:10 +0200
  Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-22 17:50 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-23 04:30 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-11-27 03:20 +0100
  Re: Discussing next steps for the Python2 removal Paul Gevers <elbrus@debian.org> - 2019-10-22 20:50 +0200
  Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-24 22:10 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-25 03:40 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-25 03:40 +0200
      Re: Discussing next steps for the Python2 removal "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2019-10-25 09:10 +0200
        Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-25 13:00 +0200
          Re: Discussing next steps for the Python2 removal Simon McVittie <smcv@debian.org> - 2019-10-28 11:00 +0100
            Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-28 11:50 +0100
      Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-25 13:00 +0200

csiph-web