On Sat, Nov 2, 2013 at 4:57 PM, Rick "Zero_Chaos" Farina <zeroch...@gentoo.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/02/2013 04:35 PM, yac wrote: >> On Sat, 02 Nov 2013 15:20:41 -0400 >> "Rick \"Zero_Chaos\" Farina" <zeroch...@gentoo.org> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >> >>> On 11/02/2013 11:03 AM, Michał Górny wrote: >>>> Dnia 2013-11-02, o godz. 14:51:26 >>>> Tom Wijsman <tom...@gentoo.org> napisał(a): >>>> >>>>> On Sat, 02 Nov 2013 09:16:45 -0400 >>>>> "Anthony G. Basile" <bluen...@gentoo.org> wrote: >>>>> >>>>>> This is a followup to a discussion on IRC yesterday regarding >>>>>> breakage that's occurring to catalyst builds as a result of the >>>>>> recent move from dev-python/python-exec to dev-lang/python-exec. >>>>> >>>>> This has been happening to users as well, for example: >>>>> >>>>> http://forums.gentoo.org/viewtopic-t-973998.html >>>>> http://forums.gentoo.org/viewtopic-t-974412.html >>>>> >>>>> To move forward and get this resolved, some questions: >>>>> >>>>> 1. Has this been resolved for users? Do they just need to sync? >>>>> 2. If not resolved for users, what is the best temporary >>>>> workaround? 3. Are you able to fix this? Do you need help to fix >>>>> this? 4. Depending on the nature of the fix: Would a news item be >>>>> needed? >>>> >>>> From what I heard, most of people get this working through a plain: >>>> >>>> emerge -Du @world >>>> >>>> If someone is really reluctant to world updates, it is enough to >>>> upgrade dev-python/python-exec to 10000.*: >>>> >>>> emerge -1v dev-python/python-exec >>>> >>>> I was considering writing a news item for it but we discussed it on >>>> IRC and decided that users are really expected to be able to handle >>>> themselves, especially wrt to: >>>> >>>> 1. using 'emerge -Du @world' to upgrade their systems, >>>> >>>> 2. reading the blocker output to see that it states >>>> '<dev-python/python-exec-10000' -> which suggests: what if I >>>> upgrade to 10000? >>>> >>>> If you believe that a news item would be helpful, I'm happy to write >>>> it. Just please make sure that we're all in agreement over the >>>> method of handling the issue. >> >>> A news item isn't enough for breaking autobuilds. If we can't find a >>> way to do this properly so portage knows how to upgrade then it is >>> being done WRONG. >> >>> Autobuilds break, gentoo can't be installed, the distro dies. I know, >>> sounds like I'm making something out of nothing but every time people >>> look at the stages and notice they are months out of date we find >>> another blog post announcing how gentoo is dead. >> >>> Honestly, if I knew a way to fix this I would have already made any >>> changes needed to fix it. Please fix this, because if you don't, >>> eventually I'll find a way and I doubt you will like it. >> >> I guess you can run a basic QA like that the image boots and gets the >> network up with openQA (or using the same method) at least to detect >> such breakage. >> > I think everyone involved knows that manual intervention is needed to > resolve this dep. I'm sure that things were tested before they were > commited, which leads me to believe that the commiter didn't care that > manual intervention is required. Sadly, we at releng do. I am actively > seeking a resolution for this, let's see who commits it first. >
In most cases, manual intervention is not required, and portage does the right thing when you run emerge -uD world. If you actually look at the deps in the tree, it really SHOULD work, and the fact that it can be resolved manually indicates that we are running into some portage weirdness. After it was committed, we starting getting a few reports of cases where it does not work without some manual intervention (including releng). I do not believe we have discovered any useful pattern, other than that is seems to happen more frequently with people who do not run full world updates.
