From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A113C138334 for ; Fri, 6 Dec 2019 08:11:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C7428E087A; Fri, 6 Dec 2019 08:11:15 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5B1BCE0824 for ; Fri, 6 Dec 2019 08:11:15 +0000 (UTC) Received: from 8f38-32b5-1620-0098-3080-83b5-07d0-2001.dyn.estpak.ee (8f38-32b5-1620-0098-3080-83b5-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:83b5:3080:98:1620:32b5:8f38]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: leio) by smtp.gentoo.org (Postfix) with ESMTPSA id BE68B34D7B4 for ; Fri, 6 Dec 2019 08:11:13 +0000 (UTC) Message-ID: Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade From: Mart Raudsepp To: gentoo-dev@lists.gentoo.org Date: Fri, 06 Dec 2019 10:11:07 +0200 In-Reply-To: <20f5820a902edd121bd49195c4adc2f5cea84fa8.camel@gentoo.org> References: <51dddccd576fb1203457a09f305bac5a48eaae6c.camel@gentoo.org> <20f5820a902edd121bd49195c4adc2f5cea84fa8.camel@gentoo.org> Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-p3Et5n6aMOB8mbOpHjeM" User-Agent: Evolution 3.32.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 9dc45521-dd06-454d-a1e4-3b251dc5f7c4 X-Archives-Hash: 0d28b2bd09ee5c3666ce42a4845adae0 --=-p3Et5n6aMOB8mbOpHjeM Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =C3=9Chel kenal p=C3=A4eval, N, 05.12.2019 kell 23:23, kirjutas David Seife= rt: > When we started removing Qt4, tons of code still used it. To put > things > in perspective: >=20 > grep -rl 'IUSE.*python_targets_python2_7' /usr/portage/metadata/md5- > cache/ | wc -l >=20 > gives me 7070 ebuilds currently. 7070 is easily more than one and > closer to two orders of magnitude more ebuilds using python 2 than > Qt4 > back in the days. You are dramatizing things too much on purpose here. That gives you a list of almost all PYTHON_COMPAT packages, the majority of which support python3 already, and will happily continue working after the user drops python2_7 from PYTHON_TARGETS or it gets dropped from the _PYTHON_ALL_IMPLS list in python-utils-r1.eclass. > Removing maintainer-needed and other semi-dead > packages is part of a proactive strategy in continuously removing and > treecleaning stale stuff from the tree. That's the problem right here. The mask included packages that are not maintainer-needed, nor maintained by python@ or other projects you or Aaron are active members of. And it was a careless mask, masking even some things that aren't even affected, merely had python2 mentioned in some commented out stuff, afaiu. I don't think there would be such a huge outcry if this was done right - involving the actual maintainers of these packages, not just going ahead and package.masking them from under them 150+ days ahead of time of actual upstream python2 last release. Presumably most of these maintainers would already know whether the package is in the progress of being ported upstream (and just needs probably less than 120 days to complete that work and make a release), or know that it's dead and go away. Or they don't respond, and you can p.mask them on a maintainer honoring timeout. As this was done is completely unacceptable. Honor your fellow maintainers and don't trample over them like this. We already are in a lack of manpower, don't chase more away by trying to take the easy route and doing stuff like this without involving them via a tracker bug or other proper ways. If you don't maintain a package, you get to work with the maintainer, not do as you please without involving them at all. I am not aware of QA having such blanket authority either for such a case. I don't think anyone can have a valid problem with package.mask of some of the things mentioned (sabnzbd, abcde, etc), because they were indeed maintainer-needed or sound@ (which David is part of, and is known crickets territory) or whatnot. It seems to have found interested maintainers, as is normal with last-rite type of package.masks. But by including things that are actually maintained, without any apparent involvement of those maintainers, you allow for such outcry even for things that shouldn't be a problem, because you display ill intent and dishonoring towards your fellow maintainers. Honor your fellow Gentoo maintainers. Period. Mart --=-p3Et5n6aMOB8mbOpHjeM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQKTBAABCgB9FiEEUdZn9pOq0mlNjRvdEKbJ+k9JlgYFAl3qDRxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUx RDY2N0Y2OTNBQUQyNjk0RDhEMUJERDEwQTZDOUZBNEY0OTk2MDYACgkQEKbJ+k9J lgbOrw/+NToYf/nMLn28I5A9CM/YUGGSO8hSdT5sOrpcgh3r2dCjvhSsTon42FHC D8wAGlukL/3QYPkqg777osDLS3zBxa3PFcp+7P6hCtRwQYnzfM4FAmeJa1xf1oO6 COROqkQlPFd3eq+ODr0VTOsLEUhJ4+mcofFhAAmixIe2dphu5kgnEP4vWCYhfnj1 a0CMPXa+NYz7e0iJyedlqz7NZ1HY5hXIg8MewVnmqNnsCS03N3EPGaU/bUSeEjAt KIGbk66OQ4MJMt2OAgRdI2SDjqcCo9dMqJzGkWvHEI9QNj0G40uXjdnsIieLmH7G 0YXPA3KWqHAdW7opiEGSZJBbubvMQ7XKG8oe60xWFPO8WyeAtINdYXH5JnB3/tNm M33mLJu+uxw662ImjFw38g5aJ/SCoNYadeqiiuNmRgoPk3s4HZDN+AwEfFf2sKGM AeQxkAv0qDe4lWFPgHHrvq0Jh5mDJAXs7rptfG9xlOxuSs4mm8Mn1O6iPtGM3PE7 yb4bzPyF1l3TIUIWz7QhXvlulZD93QnANz38kOGp/i2RhleW0Z48rtrg3wBdEqC5 Gvkfd7Sw2kkiBOJ7sMmsixhYnys7waB7ESbUe3h2jumNVAuzNIP+AEMXjH2OF5AX YUhF0hlaTNtt4iPNcSdZulZAahx2WeFpbm9ltKUvTCKmoLj09Mw= =BWFM -----END PGP SIGNATURE----- --=-p3Et5n6aMOB8mbOpHjeM--