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 DDEA5138334 for ; Thu, 2 Jan 2020 20:32:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 38349E0992; Thu, 2 Jan 2020 20:32:22 +0000 (UTC) Received: from mail.sf-mail.de (mail.sf-mail.de [IPv6:2a01:4f8:1c17:6fae:616d:6c69:616d:6c69]) (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 93230E0980 for ; Thu, 2 Jan 2020 20:32:21 +0000 (UTC) Received: (qmail 6381 invoked from network); 2 Jan 2020 20:25:03 -0000 Received: from dyn.ipv6.net-htp.de ([2a02:560:4274:2400:5012:f09c:8503:9eb]:45596 HELO daneel.sf-tec.de) (auth=eike@sf-mail.de) by mail.sf-mail.de (Qsmtpd 0.36dev) with (DHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA for ; Thu, 02 Jan 2020 21:25:03 +0100 From: Rolf Eike Beer To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Keywordreqs and slacking arch teams Date: Thu, 02 Jan 2020 21:32:12 +0100 Message-ID: <3197490.ugo6OjCCXa@daneel.sf-tec.de> In-Reply-To: <20191229000543.001631d9@katipo2.lan> References: <20191228093509.GB2033@gentoo.org> <20191229000543.001631d9@katipo2.lan> 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 Content-Type: multipart/signed; boundary="nextPart2129844.PYVLYSbMik"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-Archives-Salt: 2882e5eb-4197-4094-ac25-558cb76a5688 X-Archives-Hash: f41db49678599558e40ceebc8bf44a7a --nextPart2129844.PYVLYSbMik Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" > - Allowed a simple "Add keyword(s) for package " interface, > that intelligently created an issue and a target list, and then once > the list was built, constantly ensured the list to be valid, or > determined automatically when sub-work was completed and reducing the > published list automatically, and then responded to potential issues > based on changes in git, ( as opposed to being only triggered when > the bug was touched ) As someone who does both keywordings and stabilizations regularly on hppa and sparc I think I must share a bit of my experiences: -some arches are regularly forgotten to be CC'ed, which happens for the above arches quite regularly as they are exp -if I need to do a bug at a later point when I want to newly stabilize a given package for a new arch it is extremely helpful if - the package list was not reduced on a later point because parts were already handled - arch specifications for packages are reduced to the absolute need, i.e. especially not given if the arch list would match the initial CC list I use tatt for my work, and that automatically sorts out all packages that have non-matching package list. Sure, there could be improvements for several things in tatt, but that is IMHO absolutely right the way it is. So if you give all arches and I later decide to do the same bug on an additional arch then it will not do a single package. So if you want my work easier, then -don't forget to CC exp arches -don't clean the package list only because packages are already done -let tatt run on your dev box, or preferably in a new chroot yourself, on your package, and fix all the broken dependencies and stuff there yourself. Your amd64 laptop is still way faster than my crowded C8000, and doing a roundtrip through the bugtracker until you find time to fix it will just make you think of "slacking arch teams" next time. Thanks, Eike --nextPart2129844.PYVLYSbMik Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQSaYVDeqwKa3fTXNeNcpIk+abn8TgUCXg5TTAAKCRBcpIk+abn8 TkdqAJ4pvGb3u6aMr3BV6pM3rd65nmyblwCbBmFOTkXRK2XSCCIhJXcsaDfkEYc= =rree -----END PGP SIGNATURE----- --nextPart2129844.PYVLYSbMik--