public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Gaydenko <a@gaydenko.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: qt3support conflict
Date: Sun, 28 Jun 2009 04:35:07 +0400	[thread overview]
Message-ID: <200906280435.07716.a@gaydenko.com> (raw)
In-Reply-To: <h268ka$5t8$1@ger.gmane.org>

On Sunday 28 June 2009 03:05:48 Nikos Chantziaras wrote:
> On 06/28/2009 01:51 AM, Andrew Gaydenko wrote:
> > On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote:
> >> 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?
>
> I did not add qt3support anywhere.  It seems to be enabled by default
> here.  Anyway, you went past that problem anyway.  Your current is
> something else: the blockers.  What portage version are you using?  If
> portage won't resolve those blockers automatically for you, you can do
> it the "traditional" way.  Unmerge all packages that would be updated
> and then update again.  I would do it like this:
>
>    emerge -aC `qlist -IC x11-libs/qt*:4`
>    emerge -auDN world

Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like qt3support
flags deletion doesn't work for me. Now, after upgrading, I have tried to comment out
those flags in package.use and got conflicts (below).

===========================================

emerge -pvDuN world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] x11-libs/qt-core-4.5.2  USE="glib iconv ssl -debug -doc -pch -qt3support*" 0 kB
[ebuild   R   ] x11-libs/qt-gui-4.5.2  USE="accessibility cups dbus glib mng tiff -debug -gtk -nas -
nis -pch -qt3support* -raster -xinerama" 0 kB
[ebuild   R   ] x11-libs/qt-opengl-4.5.2  USE="-debug -pch -qt3support*" 0 kB                                                                    

Total: 3 packages (3 reinstalls), Size of downloads: 0 kB

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:                

x11-libs/qt-core:4

  ('ebuild', '/', 'x11-libs/qt-core-4.5.2', 'merge') pulled in by
    ~x11-libs/qt-core-4.5.2[glib,-debug,-qt3support] required by ('ebuild', '/', 'x11-libs/qt-
gui-4.5.2', 'merge')
    ~x11-libs/qt-core-4.5.2[-debug,-qt3support] required by ('ebuild', '/', 'x11-libs/qt-
opengl-4.5.2', 'merge')  
    (and 19 more)                                                                                                 

  ('installed', '/', 'x11-libs/qt-core-4.5.2', 'nomerge') pulled in by
    >=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/', 'kde-
base/kfourinline-4.2.4', 'nomerge')
    >=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/', 'kde-
base/ksystraycmd-4.2.4', 'nomerge')
    >=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/', 'kde-base/bomber-4.2.4', 
'nomerge')
    (and 274 more)

x11-libs/qt-gui:4

  ('installed', '/', 'x11-libs/qt-gui-4.5.2', 'nomerge') pulled in by
    ~x11-libs/qt-gui-4.5.2[qt3support] required by ('installed', '/', 'x11-libs/qt-core-4.5.2', 
'nomerge')
    >=x11-libs/qt-gui-4.4:4[qt3support,dbus] required by ('installed', '/', 'net-im/psi-0.12.1', 
'nomerge')
    ~x11-libs/qt-gui-4.5.2[qt3support,accessibility,-debug] required by ('installed', '/', 'x11-
libs/qt-qt3support-4.5.2', 'nomerge')
    (and 286 more)

  ('ebuild', '/', 'x11-libs/qt-gui-4.5.2', 'merge') pulled in by
    ~x11-libs/qt-gui-4.5.2[-debug,-qt3support] required by ('ebuild', '/', 'x11-libs/qt-opengl-4.5.2', 
'merge')
    (and 286 more)


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in the
dependencies of two different packages, then those packages can not be
installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man page
or refer to the Gentoo Handbook.




  reply	other threads:[~2009-06-28  0:35 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
2009-06-27 23:05         ` Nikos Chantziaras
2009-06-28  0:35           ` Andrew Gaydenko [this message]
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=200906280435.07716.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