| 1 |
pango could be built without cairo support, the configure script should |
| 2 |
have checked if pango was built with cairo support. |
| 3 |
|
| 4 |
Tamer |
| 5 |
|
| 6 |
Am 13.08.2010 19:28, schrieb Bill Longman: |
| 7 |
> On 08/13/2010 08:22 AM, Tamer Higazi wrote: |
| 8 |
>> As you told me I merged "lafilefixer" and ran lafilefixer --justfixit |
| 9 |
>> |
| 10 |
>> then I executed revdep-rebuild which wants to remerge a huge amout of |
| 11 |
>> packages who because "libpangocairo-1.0.so.0" was missing, or couldn't |
| 12 |
>> be linked at the end, revdep-rebuild wants to emerge a package called |
| 13 |
>> "eel" which is masked: |
| 14 |
>> |
| 15 |
>> !!! All ebuilds that could satisfy "gnome-base/eel" have been masked. |
| 16 |
>> !!! One of the following masked packages is required to complete your request: |
| 17 |
>> - gnome-base/eel-2.24.1 (masked by: package.mask) |
| 18 |
>> /usr/portage/profiles/package.mask: |
| 19 |
>> # Pacho Ramos <pacho@g.o> (12 Jul 2010) |
| 20 |
>> # Masked for removal in 30 days. |
| 21 |
>> # No longer developed by upstream, fails with forced as-needed (bug #277169), |
| 22 |
>> # does not compile against gnome-desktop-2.30 (bug #311563). |
| 23 |
>> |
| 24 |
>> but I want to upgrade my system, and love to solve this Pango Cairo problem.... |
| 25 |
>> |
| 26 |
>> if you have anymore ideas, I would thank you. |
| 27 |
> Do you know about the "-t" option for emerge? It shows you which package |
| 28 |
> is responsible for "pulling in" another package. |
| 29 |
> |
| 30 |
> You might also want to try "euse -I cairo" which will tell you which |
| 31 |
> packages are affected by the cairo use flag. |
| 32 |
> |
| 33 |
> Your "emerge --info" shows that you do have cairo turned on, but as Alan |
| 34 |
> states, you should show "emerge -pv pango" or "emerge -pv cairo" (or |
| 35 |
> whatever package you're trying to fix). Pango doesn't has a specific |
| 36 |
> "cairo" use flag so you may need to recompile pango's dependencies. |
| 37 |
> |
| 38 |
> Basically, what you're trying to do is step back from the package that's |
| 39 |
> giving you the trouble, and compile the packages that your problematic |
| 40 |
> package needs to function. Obviously, this is a geometric expansion to |
| 41 |
> some extent, but revdep-rebuild is there to help you solve the puzzle. |
| 42 |
> |
| 43 |
> Also, qdepends is really handy. |
| 44 |
> |
Archives