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