| 1 |
On 21/03/09 Nick Fortino said: |
| 2 |
|
| 3 |
> It seems like you are reading the message correctly, but you are focusing |
| 4 |
> on the wrong part. The problem here is gail, not gtk+. What should happen |
| 5 |
> is gail-1000 is installed as part of this upgrade, and then the block is |
| 6 |
> resolved. The output of "equery list -p gail" should tell you if gail-1000 |
| 7 |
> is masked for some reason. Unmasking gail-1000 should resolve the block, |
| 8 |
> but why it is masked in the first place is rather a mystery. |
| 9 |
|
| 10 |
msoulier@anton:~$ equery list -p gail |
| 11 |
[ Searching for package 'gail' in all categories among: ] |
| 12 |
* installed packages |
| 13 |
[I--] [ ] gnome-base/gail-1.22.3 (0) |
| 14 |
* Portage tree (/usr/portage) |
| 15 |
[-P-] [ ] gnome-base/gail-1.20.2 (0) |
| 16 |
[-P-] [ ] gnome-base/gail-1000 (0) |
| 17 |
[-P-] [ ] gnome-extra/libgail-gnome-1.20.0 (0) |
| 18 |
[-P-] [ ] gnome-extra/libgail-gnome-1.20.1 (0) |
| 19 |
|
| 20 |
I don't think it's masked. |
| 21 |
|
| 22 |
Shouldn't the newer gtk+ flag the fact that it obsoletes the need for gail? |
| 23 |
|
| 24 |
Mike |
| 25 |
-- |
| 26 |
Michael P. Soulier <msoulier@×××××××××××××.ca> |
| 27 |
"Any intelligent fool can make things bigger and more complex... It takes a |
| 28 |
touch of genius - and a lot of courage to move in the opposite direction." |
| 29 |
--Albert Einstein |
Archives