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 A73271396D9 for ; Fri, 13 Oct 2017 10:10:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83F782BC014; Fri, 13 Oct 2017 10:09:59 +0000 (UTC) Received: from smtp.gentoo.org (smtp.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 314F6E0C47 for ; Fri, 13 Oct 2017 10:09:59 +0000 (UTC) Received: from sf (host86-186-94-87.range86-186.btcentralplus.com [86.186.94.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: slyfox) by smtp.gentoo.org (Postfix) with ESMTPSA id 37A7D33BEBE; Fri, 13 Oct 2017 10:09:56 +0000 (UTC) Date: Fri, 13 Oct 2017 11:09:52 +0100 From: Sergei Trofimovich To: Yury German Cc: gentoo-dev@lists.gentoo.org, Gentoo Security Subject: Re: [gentoo-dev] Re: On dropping sparc@ from CC on bugs Message-ID: <20171013110952.2b6c8aa8@sf> In-Reply-To: <20170923210407.20af72d1@sf> References: <20170911084313.2cf9f40e@sf> <4481473.IXDqc1jNCF@localhost.localdomain> <22968.55158.799187.902608@a1i15.kph.uni-mainz.de> <20170913090344.0adcbede@sf> <3363B1E2-10B2-4ADF-B47B-6B6A8846EA4C@gentoo.org> <20170914082823.5afacd75@sf> <20170923210407.20af72d1@sf> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/bVw9EcKJk39r87zQ3KSJaFv"; protocol="application/pgp-signature" X-Archives-Salt: 54ed6439-b62a-42e9-847d-b1eb85f5c98c X-Archives-Hash: ca3987c0628b68397a0673bbb33fd7bb --Sig_/bVw9EcKJk39r87zQ3KSJaFv Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 23 Sep 2017 21:04:07 +0100 Sergei Trofimovich wrote: > On Thu, 14 Sep 2017 08:28:23 +0100 > Sergei Trofimovich wrote: >=20 > > On Wed, 13 Sep 2017 22:44:23 -0400 > > Yury German wrote: > >=20 > > Thank you! That's very helpful. A few clarifying questions below > > to be absolutely clear. > > =20 > > > OK so let me repeat the comments that were made on @dev (and expand = a bit further) and close the issue. > > >=20 > > > 1. Maintainers are free to cc the non-stable and experimental arches = as part of their call for stabilization. It is up to the maintainer of the = package to decide. > > >=20 > > > 2. This is providing that there is no problems caused by stableboy or= extra dependencies raised > > > Note: as a follow up change was made: 07:47 <@kensington> leio: b-man= : good point, dropped sparc from stable_arches > > >=20 > > > 3. Clean up is required as part of the security bug process, and if a= n arch is holding it up (example hppa before Slyfox took it over) an issue = would have to be raised with the QA team for action. [1] =20 > >=20 > > 'Cleanup' is only vulnerabe ebuild removal, not CC removal from the bug= , right? > > =20 > > > 4. Bugs will be closed without waiting for any non-security supported= arches, once the security process is complete. =20 > >=20 > > CC for exp lagging arches are not removed from the bug, right? > > =20 > > > 5. Security bugs are not re-assigned since they are assigned as a vul= nerability in bugzilla. If you need to continue work on the bug, please fee= l free to open another bug for the particular arch for stabilization, fix, = etc. > > >=20 > > > If you have any questions please let me know. > > >=20 > > >=20 > > > [1] - https://wiki.gentoo.org/wiki/Project:Security/GLSA_Coordinator_= Guide#Bugs_in_.5Bcleanup.5D_status =20 >=20 > Ping. Ping^2 --=20 Sergei --Sig_/bVw9EcKJk39r87zQ3KSJaFv Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSZKa0VG5avZRlY01hxoe52YR/zqgUCWeCQ8AAKCRBxoe52YR/z qrpYAJ92X38szq+okZsH2EK4Ojm6/JNBNwCdHTLXgNe2LWx/aMxfO1XlYUMnuRc= =ENBU -----END PGP SIGNATURE----- --Sig_/bVw9EcKJk39r87zQ3KSJaFv--