Path: csiph.com!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: Paul Gevers Newsgroups: linux.debian.maint.python,linux.debian.devel.release Subject: Re: Severity bump script Date: Thu, 05 Dec 2019 12:10:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Dec 5 11:07:39 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.534 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_SCAM1=0.1, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, SARE_FWDLOOK=1.666] 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="4roQQabFqJ3rZGISN0xQyfxOp4XbqkqbT" X-Mailing-List: archive/latest/17706 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a7be89f7-8e49-f32d-9d3c-5c502538fc4f@debian.org Approved: robomod@news.nic.it Lines: 93 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python , Debian release team X-Original-Date: Thu, 5 Dec 2019 12:07:21 +0100 X-Original-Message-ID: X-Original-References: <349bb59d7f28ad6c70e567d9939b99f2f924d01a.camel@ondrej.org> <153751f7-2d80-3e4c-feb1-ea8b53767946@debian.org> Xref: csiph.com linux.debian.maint.python:12110 linux.debian.devel.release:92461 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4roQQabFqJ3rZGISN0xQyfxOp4XbqkqbT Content-Type: multipart/mixed; boundary="mwNk0OXs1dHWGJXxvvf895DnPikEvi9kN"; protected-headers="v1" From: Paul Gevers To: Matthias Klose Cc: debian-python , Debian release team Message-ID: Subject: Re: Severity bump script References: <349bb59d7f28ad6c70e567d9939b99f2f924d01a.camel@ondrej.org> <153751f7-2d80-3e4c-feb1-ea8b53767946@debian.org> In-Reply-To: --mwNk0OXs1dHWGJXxvvf895DnPikEvi9kN Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi, On 03-12-2019 13:19, Matthias Klose wrote: > It's unfortunate that issues for some packages only get attention when = the > severity of an issue is raised. Following your proposal means that the= issue is > probably ignored forever, and you don't propose a better way going forw= ard, just > saying we should stop earlier. I don't think that's the correct choice= =2E For > now these seem to be single packages, so please could you name those, a= nd we can > look at those with a priority? That's at least a path that is forward = looking, > or feel free to propose another approach better than your current propo= sal for > not getting the attention of maintainers. I guess what I'm asking for could be fulfilled by an announcement to d-d-a with a package list (including via which package(s) they are affected) attached including the standard grouping by DD. And then some time to react. Paul PS, my original typed reply below. After having writing it, the idea above emerged. My problem with the current approach is that the way that developers learn that they (potentially transitively) (build) depend on a Python 2 package is by the autoremoval message. I don't think that is acceptable socially in the project. My proposal is to give the maintainers about those packages a heads up. Via a bug report may be a bit weird in cases, but in some cases may be the appropriate thing as the package could work around the (build) dependency. At least adding "affects" helps a tiny bit and direct e-mails to the maintainers (e.g. via the @packages.debian.org address will at least give them a heads up. Even if the RM bug is coming eventually. Again, I don't have a problem with Python 2 removal, even at the price of packages that don't care that their dependency is written in Python. I do care about proper communication. Using RC severity to trigger autoremoval for non-leaf packages just yet is not appropriate in the opinion of the release team. Even though I am well aware of the Python 2 removal effort I can tell from personal experience (cacti) that receiving an autoremoval e-mail as the first sign of such a dependency isn't nice, that's the problem I'm having and that needs solving in my opinion. --mwNk0OXs1dHWGJXxvvf895DnPikEvi9kN-- --4roQQabFqJ3rZGISN0xQyfxOp4XbqkqbT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3o5OoACgkQnFyZ6wW9 dQqexwgAs+0Ur94Xlak13OxRPSUNr9Nupmxg77jlHtPXGN7jP81kztDJl9CK4tBV CqjWMgW6k96NC3KFO+Ap7E2pYq7GBQF/xWHgYR2Yg4i6c18gbcSDlBGlqQQR/2Ek R+isNRAYCx9sRw/cKUCN27pulocvGQ7ksh8EqhpqzKwD9SyxQA7RvedRFCkIM1Cg TDqCCnbOj7Ba1MjsVj7prcthpnprpgKe6s4aIEeTWu1uzPy48kcnMxbUwzyuKC1d CQ5zo59Ge+7FqHH4plzEZ+9nN3Si/U6LDZqmObCt49FgvS9SyOyklKMg3j+i8n7q QsvchhUIWyy/N/meE8Jj7XcLCkg0oQ== =WoQd -----END PGP SIGNATURE----- --4roQQabFqJ3rZGISN0xQyfxOp4XbqkqbT--