| 1 |
On 09/01/2009 05:00 PM, James wrote: |
| 2 |
> walt<w41ter<at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Did you then re-emerge alsa-lib after that change? I believe that's |
| 6 |
>> what it wants you to do before trying to update kde. |
| 7 |
> |
| 8 |
> |
| 9 |
> Yep. But that does not fix the general upgrade problem. |
| 10 |
> |
| 11 |
> |
| 12 |
> After successfully emerging |
| 13 |
> alsa-lib-1.0.20-r1 upgrade attempts still are met by: |
| 14 |
> |
| 15 |
> |
| 16 |
> emerge: there are no ebuilds built with USE flags to satisfy |
| 17 |
> "media-libs/alsa-lib[midi]" |
| 18 |
> |
| 19 |
> Maybe I should try the kernel approach to Alsa? |
| 20 |
|
| 21 |
The correct answer is "I don't know". I use gnome, not kde, as my |
| 22 |
desktop, but I do like the k3b disc-burner app, so I have the minimal |
| 23 |
kde and qt libs to support k3b. |
| 24 |
|
| 25 |
I recently ran into upgrade problems with my minimal qt/kde system |
| 26 |
that I fixed simply by deleting every package depending on either qt |
| 27 |
or kde, and all problems were magically fixed. (Don't ask me why.) |
| 28 |
|
| 29 |
Pain in the butt, but maybe worth the pain. |
Archives