From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] portage-2.3.2 stable request?
Date: Fri, 4 Nov 2016 16:15:16 -0700 [thread overview]
Message-ID: <1d9fab70-7a81-5816-3a20-ab89dd14528a@gentoo.org> (raw)
In-Reply-To: <67ea611d-e71d-590d-6088-ce4f627bcd32@gentoo.org>
On 11/04/2016 03:55 PM, Zac Medico wrote:
> On 11/04/2016 03:47 PM, Brian Dolbec wrote:
>> On Fri, 4 Nov 2016 13:53:02 -0700
>> Zac Medico <zmedico@gentoo.org> wrote:
>>
>>> On 11/04/2016 01:43 PM, Michał Górny wrote:
>>>> On Fri, 4 Nov 2016 13:19:39 -0700
>>>> Zac Medico <zmedico@gentoo.org> wrote:
>>>>
>>>>> On 11/04/2016 01:14 PM, Brian Dolbec wrote:
>>>>>> On Thu, 3 Nov 2016 15:55:23 -0700
>>>>>> Zac Medico <zmedico@gentoo.org> 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.
Let's just revert the emerge-webrsync patch, so we can tag a 2.3.3
release on the master branch.
--
Thanks,
Zac
next prev parent reply other threads:[~2016-11-04 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 22:55 [gentoo-portage-dev] portage-2.3.2 stable request? Zac Medico
2016-11-04 20:14 ` Brian Dolbec
2016-11-04 20:19 ` Zac Medico
2016-11-04 20:43 ` Michał Górny
2016-11-04 20:53 ` Zac Medico
2016-11-04 22:47 ` Brian Dolbec
2016-11-04 22:55 ` Zac Medico
2016-11-04 23:15 ` Zac Medico [this message]
2016-11-05 12:56 ` Manuel Rüger
2016-11-06 17:34 ` Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d9fab70-7a81-5816-3a20-ab89dd14528a@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox