I'm not sure about the downgrade from 3.3.6 to 3.3.5, but I had the same problem with libungif. I fixed it by unmerging giflib (emerge --ask --unmerge media-libs/giflib). Then re-running the update, which actually re-installed giflib for me.
HTH
On 9/14/05, Yann GARNIER <[EMAIL PROTECTED]> wrote:
Hi all,
I did an "emerge -vuD world" last week and, among other thing, it updated GCC from 3.3.5 to 3.3.6 (which seemed to be a good thing..)
Today after an "emerge --sync" I wanted to re-update my system ... and I'm wondering why portage 'wants' to downgrade my version of GCC from 3.3.6
to 3.3.5... but also wondering why it suddenly wants to install giflib (which is blocked because of libungif...)
The only thing I can do now to update the system is to add "-gif" in my make.conf file.
Is there any other way to solve the giflib/libungif conflict ?
What makes portage want to install giflib ?
Can someone tell me what I missed ?
In advance thank you.
Yann Garnier
--
gentoo-user@gentoo.org mailing list
