From: James Colby <jcolby@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage question...
Date: Wed, 14 Sep 2005 10:09:42 -0400 [thread overview]
Message-ID: <c001995e05091407094ac3bd4e@mail.gmail.com> (raw)
In-Reply-To: <24445484.1126705865406.JavaMail.www@wwinf1603>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Yann -
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 <garnier-yann@wanadoo.fr> 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
>
>
[-- Attachment #2: Type: text/html, Size: 1507 bytes --]
next prev parent reply other threads:[~2005-09-14 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 13:51 [gentoo-user] Portage question Yann GARNIER
2005-09-14 14:09 ` James Colby [this message]
2005-09-14 15:46 ` Peter Ruskin
2005-09-14 22:14 ` Yann Garnier
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 14:01 [gentoo-user] portage question Eric Crossman
2005-10-05 14:46 ` Michael Crute
2005-10-05 14:50 ` Holly Bostick
2005-10-06 15:30 ` Eric Crossman
2006-04-20 15:55 Dan LaMotte
2006-04-21 9:33 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c001995e05091407094ac3bd4e@mail.gmail.com \
--to=jcolby@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox