On Sat, Mar 26, 2011 at 12:56 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>
>> I've been through this 2.7 update process on 4 machines now. It seems
>> on all of my machines the python-updater thing is pretty much always
>> broken with respect to:
>>
>> openoffice-bin
>> boost
>> emul-linux-x86-baselibs
>>
>> No matter how many times I rerun things it just wants to keep rebuilding
>> them.
>>
>> What's weird is that no two machine see exactly the same. Some only
>> fail with one of those packages, others fail with 2 or 3. Rerunning
>> phython-updater, or lafilefixer, or revdep-rebuild or removing them
>> completely and letting emerge -DuN @world reinstall them changes
>> nothing. They just go on failing the same way.
>>
>> Waste of time so far...
>
> If you machines are running stable arch there was also this that came up
> today:
>
> revdep-rebuild -v --library 'libmpfr.so.1' -- --ask
>
> Check your elog in case there are some more packages that need revdep-rebuild.
>
> --
> Regards,
> Mick
>
I had nothing linked to libmpfr.so.1 so that wasn't the root cause/
In my case it seems to be driven by bugs like this:
http://bugs.gentoo.org/show_bug.cgi?id=360425
Seems the only thing to do it just wait for devs to fix it. (And
wonder why something like python-2.7 gets released as stable with
stuff like this hanging about....)
Cheers,
Mark
The libmpfr change bit me on one of my amd64 machines. I did the revdep-rebuild on the library and then gcc was broken. I recompiled everything but still sandbox and gcc won't compile.
--
Bill Longman