1 |
On Sat, Mar 26, 2011 at 12:56 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
>> |
3 |
>> I've been through this 2.7 update process on 4 machines now. It seems |
4 |
>> on all of my machines the python-updater thing is pretty much always |
5 |
>> broken with respect to: |
6 |
>> |
7 |
>> openoffice-bin |
8 |
>> boost |
9 |
>> emul-linux-x86-baselibs |
10 |
>> |
11 |
>> No matter how many times I rerun things it just wants to keep rebuilding |
12 |
>> them. |
13 |
>> |
14 |
>> What's weird is that no two machine see exactly the same. Some only |
15 |
>> fail with one of those packages, others fail with 2 or 3. Rerunning |
16 |
>> phython-updater, or lafilefixer, or revdep-rebuild or removing them |
17 |
>> completely and letting emerge -DuN @world reinstall them changes |
18 |
>> nothing. They just go on failing the same way. |
19 |
>> |
20 |
>> Waste of time so far... |
21 |
> |
22 |
> If you machines are running stable arch there was also this that came up |
23 |
> today: |
24 |
> |
25 |
> revdep-rebuild -v --library 'libmpfr.so.1' -- --ask |
26 |
> |
27 |
> Check your elog in case there are some more packages that need |
28 |
revdep-rebuild. |
29 |
> |
30 |
> -- |
31 |
> Regards, |
32 |
> Mick |
33 |
> |
34 |
|
35 |
I had nothing linked to libmpfr.so.1 so that wasn't the root cause/ |
36 |
> |
37 |
> In my case it seems to be driven by bugs like this: |
38 |
> |
39 |
> http://bugs.gentoo.org/show_bug.cgi?id=360425 |
40 |
> |
41 |
> Seems the only thing to do it just wait for devs to fix it. (And |
42 |
> wonder why something like python-2.7 gets released as stable with |
43 |
> stuff like this hanging about....) |
44 |
> |
45 |
> Cheers, |
46 |
> Mark |
47 |
> |
48 |
> |
49 |
The libmpfr change bit me on one of my amd64 machines. I did the |
50 |
revdep-rebuild on the library and then gcc was broken. I recompiled |
51 |
everything but still sandbox and gcc won't compile. |
52 |
|
53 |
-- |
54 |
Bill Longman |