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 458361395E1 for ; Fri, 4 Nov 2016 22:55:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68B9BE0B32; Fri, 4 Nov 2016 22:55:39 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 43FEFE0B12 for ; Fri, 4 Nov 2016 22:55:39 +0000 (UTC) Received: from [10.128.12.228] (unknown [100.42.98.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 0A98734164F for ; Fri, 4 Nov 2016 22:55:36 +0000 (UTC) Subject: Re: [gentoo-portage-dev] portage-2.3.2 stable request? To: gentoo-portage-dev@lists.gentoo.org References: <2275c91d-8320-2876-6b4b-81e976fe9eee@gentoo.org> <20161104131422.585a1e73.dolsen@gentoo.org> <20161104214301.720543d2.mgorny@gentoo.org> <20161104154709.19bdc863.dolsen@gentoo.org> From: Zac Medico Message-ID: <67ea611d-e71d-590d-6088-ce4f627bcd32@gentoo.org> Date: Fri, 4 Nov 2016 15:55:35 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20161104154709.19bdc863.dolsen@gentoo.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 43e89a93-cf54-4ca7-b864-640d691253b5 X-Archives-Hash: 15a931f4878787e8d99fd342bdd986c9 On 11/04/2016 03:47 PM, Brian Dolbec wrote: > On Fri, 4 Nov 2016 13:53:02 -0700 > Zac Medico wrote: > >> On 11/04/2016 01:43 PM, Michał Górny wrote: >>> On Fri, 4 Nov 2016 13:19:39 -0700 >>> Zac Medico wrote: >>> >>>> On 11/04/2016 01:14 PM, Brian Dolbec wrote: >>>>> On Thu, 3 Nov 2016 15:55:23 -0700 >>>>> Zac Medico wrote: >>>>> >>>>>> In about a week, portage-2.3.2 will be eligible for a stable >>>>>> request. >>>>>> >>>>>> The only potential problem that I've noticed is the complaint >>>>>> about changes from bug 552814 causing issues for people using >>>>>> git sync with overlay filesystems, but setting sync-depth = 0 >>>>>> gives those users a workaround. There's also bug 597838, about >>>>>> the sync-depth setting being ineffective, but I only know of a >>>>>> couple of people that have been able to reproduce that. >>>>>> >>>>>> So, do we want to do a stable request portage-2.3.2 when the time >>>>>> comes? >>>>> >>>>> I'm not sure. Do we -r1 it adding a patch or two and ask it be >>>>> stabled? >>>> >>>> There are just 4 commits since 2.3.2, and they all look good. >>>> Maybe we should just cut a 2.3.3 release and wait another 30 days >>>> (we also need to stabilize app-crypt/gkeys since it's needed by >>>> emerge-webrsync now). >>> >>> Wouldn't it be better to have a really working version of gkeys >>> before it's stabilized? Like one that could be used without having >>> to create custom configuration files and/or run it as root? >> >> Well, gkeys stabilization is not really mandatory, since >> emerge-webrsync has a --insecure option. > > Why don't I/we work on whatever changes are needed to merge the > meta-manifest code to both portage and gkeys. I'll push out another > release. I also had some initial code that added gkeys use to verify > the pkg Manifest file, but I don't know if that is needed still, the > meta-manifest system will need to run a verify at the end of the sync. > > We'll have to poke Robin some more to get some new infra keys setup. > > If I have to, maybe I'll create some ansible scripts to run the dev > seeds update on vulture, transfer it to my system to push --sign to > api.g.o or break down and get Kristian to help me get key forwarding > better setup so I can do it from vulture. Sounds good, but I think we should cut a portage 2.3.3 release before we make any more changes. Maybe do a release branch that includes everything except the emerge-webrsync change. -- Thanks, Zac