From: Andrew Gaffney <agaffney@technaut.darktalker.net>
To: Gentoo Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] wxGTK {up|down}grade loop
Date: Sat, 25 Oct 2003 12:58:28 -0500 [thread overview]
Message-ID: <3F9AB9C4.70506@technaut.darktalker.net> (raw)
In-Reply-To: <1067103837.16419.1.camel@neferteti>
Ruben Vermeersch wrote:
> Ok, here's what's bugging me lately:
>
> ruben@neferteti ruben $ emerge -uDp world
>
> These are the packages that I would merge, in order:
>
> Calculating world dependencies ...done!
> [ebuild U ] x11-libs/wxGTK-2.4.1-r1 [2.4.0]
>
> After updating wxGTK, i stumble upon this:
>
> neferteti ruben # emerge -uDp world
>
> These are the packages that I would merge, in order:
>
> Calculating world dependencies ...done!
> [ebuild UD] x11-libs/wxGTK-2.4.0 [2.4.1-r1]
>
> Something tells me this ain't normal behaviour :)
I've seen this kind of thing a few times before, most notably with avifile and drip. In
this case, there is an update available for wxGTK, so portage upgrades it. Unfortunately,
there is some program installed that requires on a version of wxGTK <=2.4.0, so portage
downgrades it to not break the other program. I consider this behavior a portage bug, but
as far as I know, there is currently no easy way to prevent this from happening.
--
Andrew Gaffney
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-25 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 17:43 [gentoo-dev] wxGTK {up|down}grade loop Ruben Vermeersch
2003-10-25 17:58 ` Andrew Gaffney [this message]
2003-10-25 20:00 ` Paul de Vrieze
2003-10-25 20:23 ` Andrew Gaffney
2003-10-25 20:39 ` Paul de Vrieze
2003-10-25 20:58 ` Paul de Vrieze
2003-10-25 23:17 ` Grant Goodyear
2003-10-27 6:11 ` Andrew Gaffney
[not found] ` <20031025200632.GA5274@whitestar>
2003-10-27 6:01 ` Andrew Gaffney
2003-10-25 18:16 ` Brian Jackson
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=3F9AB9C4.70506@technaut.darktalker.net \
--to=agaffney@technaut.darktalker.net \
--cc=gentoo-dev@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