Michael P. Soulier wrote:
On 21/03/09 Nick Fortino said:
It seems like you are reading the message correctly, but you are focusing
on the wrong part. The problem here is gail, not gtk+. What should happen
is gail-1000 is installed as part of this upgrade, and then the block is
resolved. The output of "equery list -p gail" should tell you if gail-1000
is masked for some reason. Unmasking gail-1000 should resolve the block,
but why it is masked in the first place is rather a mystery.
msoul...@anton:~$ equery list -p gail
[ Searching for package 'gail' in all categories among: ]
* installed packages
[I--] [ ] gnome-base/gail-1.22.3 (0)
* Portage tree (/usr/portage)
[-P-] [ ] gnome-base/gail-1.20.2 (0)
[-P-] [ ] gnome-base/gail-1000 (0)
[-P-] [ ] gnome-extra/libgail-gnome-1.20.0 (0)
[-P-] [ ] gnome-extra/libgail-gnome-1.20.1 (0)
I don't think it's masked.
Shouldn't the newer gtk+ flag the fact that it obsoletes the need for gail?
Mike
Hmm, that's odd. gtk+ does flag the fact that it includes gail with the
block you are running into, and gail-1000 is used to make programs which
depend on gail happy. emerge -uDN world should really just take care of
this, as gail should be upgraded to gail-1000.
At the end of the day, Daniel is right, unmerging gail should resolve
the block, and everything should work when you are done upgrading.
Portage should (and did for me) take care of this on it's own though.
Nick
