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 A3A6E138334 for ; Sat, 28 Dec 2019 07:09:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 73BCFE0A98; Sat, 28 Dec 2019 07:09:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 A602EE0A92 for ; Sat, 28 Dec 2019 07:09:39 +0000 (UTC) Received: from pomiot (c142-245.icpnet.pl [85.221.142.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 900AA34DC31; Sat, 28 Dec 2019 07:09:37 +0000 (UTC) Message-ID: Subject: [gentoo-dev] Keywordreqs and slacking arch teams From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev Date: Sat, 28 Dec 2019 08:09:33 +0100 Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-ta5sTqiHAkcA/bvFQKC5" User-Agent: Evolution 3.32.5 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: 1f72dc81-7325-4315-9479-9812584f58d3 X-Archives-Hash: ebb7d9b18a355668e56a80aecaaa5448 --=-ta5sTqiHAkcA/bvFQKC5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, The Python team ends up filing a lot of keywordreqs due to new dependencies. Many of them end up open for many months, and start listing obsolete package versions. Then an arch team wakes up... and adds keywords to a version that's supposed to be removed already.=20 Or complains that the package list is outdated. I think it's generally a reasonable assumption that keywordreq should be applied to the newest version of a package, unless the keywordreq explicitly says otherwise (in the comment). It's not helpful that stable-bot requires us to fill specific versions here. I don't think it's fair to expect package maintainers to keep package versions up-to-date in this case. I can take the blame if the package list becomes outdated, say, in 1 months. If the arch team can't keyword something in 6 months, I blame them, and I believe it should be their responsibility to update the keywordreq. Otherwise, we're creating a silly workflow where I keep putting an effort into keeping the keywordreq up-to-date, hoping that one day arch teams might actually act upon it. How can we improve this? --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-ta5sTqiHAkcA/bvFQKC5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAl4G/61fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 NkE4NDUwOTQwOThEMjhDQzhCMjZDNTYzOUFEQUUyMzI5RTI0MEUACgkQY5ra4jKe JA4hfgf/ZoWbV97VSgewXsi7wtikoO9TlpMVgCkIJs0dZgPIgpwnuky30t8JuSGh KF+/WWUJEAHUAqwmXCuVUu2KTwz51JVGc/Hi3xQkoo0KX+RcUm9weFvyvJEp0DhN dhLPZpqoUXo3o0b4oh6NYtjpGDi1BrXvw/GXRdYV8XKxVpQ/RKkiBXdg7f0gcApD ly7dEkGVae7H6Kw/klhpp6j5ZU3XSStZEH74A99dVACr08JtlQtAKDGKnnlck+iX p1Ys3Cz51dptvXu5PWv8ObAEeAiebzt2p5HQzq1QZv8LuwumRJCw8ljdI4wUpGSo fGzScA4z80duRwwLNXExLP4jSjNT2Q== =MfPp -----END PGP SIGNATURE----- --=-ta5sTqiHAkcA/bvFQKC5--