Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW**

2013-05-01 Thread Zac Medico
On 05/01/2013 02:42 PM, James Cloos wrote: >> "ZM" == Zac Medico writes: > > ZM> That commit allows backtracking to continue in the event that unsolved > ZM> blockers are encountered, solving this bug: > > ZM> https://bugs.gentoo.org/show_bug.cgi?id=465638 > > I read the bug. But it was

Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW**

2013-05-01 Thread James Cloos
> "ZM" == Zac Medico writes: ZM> That commit allows backtracking to continue in the event that unsolved ZM> blockers are encountered, solving this bug: ZM> https://bugs.gentoo.org/show_bug.cgi?id=465638 I read the bug. But it was the only commit that at first glance *could* have been the

Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW**

2013-05-01 Thread Zac Medico
On 05/01/2013 01:56 PM, James Cloos wrote: >> "ZM" == Zac Medico writes: > > ZM> On 04/30/2013 11:19 PM, James Cloos wrote: >>> My typical emerge -upvDN world went up from 10s of minutes to several >>> hours sometime between portage 37f33e9 and 2d5e38b. > > ZM> I don't see any regressions on

Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW**

2013-05-01 Thread James Cloos
> "ZM" == Zac Medico writes: ZM> On 04/30/2013 11:19 PM, James Cloos wrote: >> My typical emerge -upvDN world went up from 10s of minutes to several >> hours sometime between portage 37f33e9 and 2d5e38b. ZM> I don't see any regressions on my end. Please feel free to bisect those ZM> commits