1 |
I was getting that error after syncing late last night. Here is the |
2 |
information I got on the situation that prompted me to remove |
3 |
introspection from :2 |
4 |
|
5 |
http://www.gossamer-threads.com/lists/gentoo/dev/241030 |
6 |
|
7 |
However after reading that more thoroughly and not having my system in |
8 |
front of me I think I might not have unmasked the latest version of |
9 |
pygobject:2 which uses the introspection flag not to build |
10 |
introspection support, but to automatically pull in pygobject:3 for |
11 |
it. |
12 |
|
13 |
I'm probably trying to build the old pygobject with built-in |
14 |
introspection support which conflicts with introspection in :3. |
15 |
|
16 |
So I think I finally figured out all my problems, I'll get home |
17 |
tonight after work and give it a try. Hopefully someone will Google |
18 |
this list and find this helpful, if not confusing. |
19 |
On Dec 3, 2011 10:50 AM, "walt" <w41ter@×××××.com> wrote: |
20 |
> |
21 |
> On 12/02/2011 07:37 PM, Jason Weisberger wrote: |
22 |
>> |
23 |
>> |
24 |
>> Everything is compiling perfectly, albeit without fallback mode. Any |
25 |
>> ideas for resolving the pygobject:2 introspection block so I can |
26 |
>> install it? |
27 |
>> |
28 |
>> |
29 |
>> pygobject:2 needs -introspection to be able to slot :2 and :3 on the |
30 |
>> same system. |
31 |
> |
32 |
> |
33 |
> That's not true on my system. I have pygobject-3.0.2 and 2.28.6-r50 |
34 |
> *with* introspection, and I just re-emerged both of them without problem. |
35 |
> |
36 |
> Are you still getting that error after syncing today? |
37 |
> |
38 |
> |