From: Andrew Gaydenko <a@gaydenko.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: qt3support conflict
Date: Sun, 28 Jun 2009 02:51:12 +0400 [thread overview]
Message-ID: <200906280251.12299.a@gaydenko.com> (raw)
In-Reply-To: <h2677e$32n$1@ger.gmane.org>
On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote:
> On 06/28/2009 01:32 AM, Andrew Gaydenko wrote:
> > On Sunday 28 June 2009 02:23:38 Nikos Chantziaras wrote:
> >> On 06/28/2009 12:51 AM, Andrew Gaydenko wrote:
> >>> Trying to upgrade to qt 4.5.2:
> >>>
> >>> kde4 wants qt3support for qt-core:
> >>>
> >>> x11-libs/qt-core-4.5.2 (Change USE: +qt3support)
> >>> (dependency required by "x11-libs/qt-qt3support-4.5.2" [ebuild])
> >>> (dependency required by "kde-base/kteatime-4.2.4" [installed])
> >>> (dependency required by "kde-base/kdetoys-meta-4.2.4" [installed])
> >>> (dependency required by "kde-base/kde-meta-4.2.4" [installed])
> >>>
> >>> OK, let's try:
> >>>
> >>> adding qt3support to qt-core wants qt3support for qt-gui
> >>> adding qt3support to qt-gui wants qt3support for qt-sql
> >>> adding qt3support to qt-sql conflicts with x11-libs/qt-opengl - last
> >>> one insits on -qt3support for qt-core.
> >>>
> >>> At ~amd64. Where is my mistake?
> >>
> >> You forgot to add qt3support to qt-opengl too :)
> >>
> >> Anyway, I find all this a bit strange. qt3support is on by default, why
> >> do you have to enable it explicitly? Did you put "-qt3support" in
> >> make.conf? If yes, you should remove it.
> >
> > make.conf hasn't qt3support at all. Adding qt3support to qt-opengl
> > shows... well... something horrible (see below) :-)
> >
> > //======================================================================
> > emerge -pvDuN world
> >
> > These are the packages that would be merged, in order:
> > [...]
>
> I got that too, but portage (I'm on 2.1.6.13) has automatically resolved
> all blocks. Are you using Paludis? If yes, uninstall all packages that
> are to be upgraded and install them afterwards. Or wait for someone who
> actually knows a Paludis workaround for this.
No, I don't use Paludis. What do you mean saying "has automatically resolved
all blocks"? Do you mean you have added those qt3support flags and started
emerging and got successfull upgrading to 4.5.2 without any problems and in
spite of those blocks?
next prev parent reply other threads:[~2009-06-27 22:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 21:51 [gentoo-user] qt3support conflict Andrew Gaydenko
2009-06-27 22:23 ` [gentoo-user] " Nikos Chantziaras
2009-06-27 22:32 ` Andrew Gaydenko
2009-06-27 22:41 ` Nikos Chantziaras
2009-06-27 22:51 ` Andrew Gaydenko [this message]
2009-06-27 23:05 ` Nikos Chantziaras
2009-06-28 0:35 ` Andrew Gaydenko
2009-06-28 0:55 ` Nikos Chantziaras
2009-06-28 1:12 ` Andrew Gaydenko
2009-06-28 1:41 ` Nikos Chantziaras
2009-06-27 22:54 ` walt
-- strict thread matches above, loose matches on Subject: below --
2009-06-28 2:24 Andrew Gaydenko
2009-06-28 14:12 ` walt
2009-06-28 16:46 ` Alan McKinnon
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=200906280251.12299.a@gaydenko.com \
--to=a@gaydenko.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