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? -- Best regards, Michał Górny