Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Paul Gevers Newsgroups: linux.debian.maint.python Subject: Re: Discussing next steps for the Python2 removal Date: Tue, 22 Oct 2019 20:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 22 18:41:54 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-14.3 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no Openpgp: preference=signencrypt Autocrypt: addr=elbrus@debian.org; prefer-encrypt=mutual; keydata= mQENBE2LmVYBCADS6vA01KutEM74dDGrsmT2q6Mh5C3TAyNhLigBEWNGnfbFr6AHX1EvdkC/ 7g5QcFGqiiOjTdHncRNtvUbistfbF1ynE6evD3p5tpkn6ymmVwSIjx9np7GWJgZgBo0zkpij M1iimHTs1BcZhL7WQlvVJO3Xm8jr7NpgjkRRkkPaj0Kd/HYuPGqN74pwXB7nR5Uw2ypYS0eT iCHUUTUrvgP3fqOWc2bgbCIsuoXpp/QLT5ehC+M01UKMHVUkr97cwT4wg03XqE2cL7r6szry GZMpL3CU4IsPNghfeZhRrZlk6A73OtpLxTXibydt8Og91eC2ALer28bJnn+haIaTNwc3ABEB AAG0H1BhdWwgR2V2ZXJzIDxlbGJydXNAZGViaWFuLm9yZz6JAVcEEwEIAEECGyMFCwkIBwMF FQoJCAsFFgIDAQACHgECF4ACGQEWIQRYtm1Ic2vpOwUt5nKcXJnrBb11CgUCXHRFuQUJEqsT YwAKCRCcXJnrBb11CgycB/9Kl9K85cXLGo5PJ0a4oiq53kOTuzlmFPRedMhwECQ+JrFigLe2 DH1ZhLpepzQ5Bszq5vMbiqK6Ek5yKH6NYp7ktPYQaFsqNybPaaNkkj/i1pGlnpYESuliiLQG Scj9+oGd8mD4cF1VWboLuAESW2lr2bJs3ln/7bt9CNhgKZ5h6zMJ+0ZaSjbjpv3eKu6WTquT c+/p5sU4m0WE/FSkg28SvWEcyqTuVvs63CT/CK9xeAmUaMKf18qrKX1AURyn6nf+Aqs11ATD EeTmGW08VvKSlVVrR0HLSyTOOQxEV99upobhOm2Ml4an9RrSJS1LUiEYR5QMvvDR3VJ+W6KQ GW/OuQENBE2LmVYBCAC6ZRwRIuJ2l2FYLd5/URSgkTSfwANnXWBpNOVYhuGrvveA0e9KrToI pqZCRjrAiuaW4aaQq8dwYZpCMJhq3VzVW0C0BA7QARrePEQfJXkNiHyYEoJrmt21zQO8KP1m d13TtX1jj/Sqt2Y4efbKKZ2VeWwngsgXOwCTVyj7tth6fwn+5bPptxp/Ux4CXD5G4XvGTGfR pEa61sfvh6NEZTbe/7gGFEOBSat7esVAj170NVc4V8HX+/NtlJrlEce6BMbCvug5vF4iGkMY NwbdzFu2+rB+w9Dmo262lnWtUYQpX1nnmbWS8nU7ygCcKd/xc08xYCu1gt69YHp7yOqK2Nr3 ABEBAAGJATwEGAEIACYCGwwWIQRYtm1Ic2vpOwUt5nKcXJnrBb11CgUCXHRFvwUJEqsTaQAK CRCcXJnrBb11ChElB/wJvGm3rOIuUpd1TQaCT1TGr2YHCF23+WnLfndjaBLgCaAyChfv20b1 cslCZvswy6UwTX9AvksiIZhfWE5GHXTxk1Z02bwqTWagtPTr5HBIdSGf9m1abrqknl0B50Kr wWLe9U80ch2atix0qq1nW/R9/2O3/wledNk45bEb8JzxBctMnPYMzIf53zy0hEoCLf3hm6AS vUmMd0+OFk3kUwb9S/k8jjdIw1PBi/ukexqipuUzLX9YYDlNsDLp5M9vgDQDJWfrCFbSkr4G /EEo4yh4uhWIU5rSrvrtKEQZYtXrm5x996qn79m/9CPZJarUK4PHnaN0iE+D168Yblay+e6R User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8wVgoG7Y0DyMhQzWHLCdOZ76DSVoXfmqc" X-Mailing-List: archive/latest/17481 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/99c49de9-9cdc-ed91-a603-2c429737a5bf@debian.org Approved: robomod@news.nic.it Lines: 72 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Chris Lamb X-Original-Date: Tue, 22 Oct 2019 20:41:31 +0200 X-Original-Message-ID: <99c49de9-9cdc-ed91-a603-2c429737a5bf@debian.org> X-Original-References: <10ee755b-5e97-84bc-22d8-4ed29182bf84@debian.org> Xref: csiph.com linux.debian.maint.python:11920 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8wVgoG7Y0DyMhQzWHLCdOZ76DSVoXfmqc Content-Type: multipart/mixed; boundary="u3wUWhFD0rjEtBxa3kJfsdI3216ja25rj"; protected-headers="v1" From: Paul Gevers To: Matthias Klose , debian-python Cc: Chris Lamb Message-ID: <99c49de9-9cdc-ed91-a603-2c429737a5bf@debian.org> Subject: Re: Discussing next steps for the Python2 removal References: <10ee755b-5e97-84bc-22d8-4ed29182bf84@debian.org> In-Reply-To: <10ee755b-5e97-84bc-22d8-4ed29182bf84@debian.org> --u3wUWhFD0rjEtBxa3kJfsdI3216ja25rj Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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) --u3wUWhFD0rjEtBxa3kJfsdI3216ja25rj-- --8wVgoG7Y0DyMhQzWHLCdOZ76DSVoXfmqc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2vTVwACgkQnFyZ6wW9 dQo5hgf/VlLaZ8EMRwktPXoDRfyG+PR+TARoA/9szdDtELNLhKCEujvbx57E+y1C hWlSHkXbtASz8cDVGzkggtuehNURBR+OXbF2U+s19E9y4VIEH7X9ANmTNvCG1lql S/9Qz0YIwgSvT7pa9s3lQu3nRsRJx4BnQ9KM4SpYXpjSfivngT6Bfe2UCJ4rzrEt PiTDmlEHVBgsBUk+Xr3w5kPv0lpDRCYnTw5SLvnuTi7bbXZeAvKZWP/O9yfM+yHB dKW5suylC+1OIRfaBuRDwgvdPBva9uBNex+Yj2EuLpbENJMXNyt6ztfu7uGkqPq3 R6SdIt+81sctlcymeSZkUoHzoP9LwQ== =bbJN -----END PGP SIGNATURE----- --8wVgoG7Y0DyMhQzWHLCdOZ76DSVoXfmqc--