From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Uncle: qt-*:4 dependencies/blocks preventing world update
Date: Fri, 23 Oct 2009 20:46:32 -0500 [thread overview]
Message-ID: <4AE25C78.3040008@gmail.com> (raw)
In-Reply-To: <7bef1f890910231829t4437b5a3se1cea6b509621934@mail.gmail.com>
Alan E. Davis wrote:
>
> I have read a number of different explanations and suggestions, some
> of them regarding an earlier, yet similar, tanglement between versions
> of qt-*. I've tried a number of suggestions, and I have unmerged and
> remerged packages.
>
> I am now trying to individually merge packages with dependencies on
> qt-*-4.5.2.
>
> I tried KDE 4.3.1, with some trepidation, and I have happily been
> running gnome, save a couple of nits, and I have run into qt issues in
> the past. I would like to uninstall kde4 (like it, but not well
> enough to devote so many resources to it, and to have to upgrade
> frequently and painfully). I would like to remove the KDE 4
> installation, but keep the individual packages depending on kdelibs.
> (K3b, etc.). Would this have an impact on this issue? This is off
> topic, but how to uninstall EXCEPT what I want, of KDE4? Is this
> reasonable?
>
> Thanks. I hope to solve this soon, but it's too early to know
> whether the help on this list was enough. I changed USE flags, and
> the same messages appear:
>
> <<SNIP >>
>
> Thank you,
>
> Alan
>
Does this help any?
root@smoker / # eselect news read 6
2009-09-27-qt_use_changes
Title Qt 4.5.2 default USE flag changes
Author Alex Alexander <wired@gentoo.org>
Posted 2009-09-27
Revision 1
Qt version 4.5.2 has significant changes in the USE flags enabled by
default.
When upgrading, make sure you check and re-enable any USE flags you
need.
Depending on your system and installed packages, you might hit an issue
where Portage is getting confused by this USE flag change, trying to mix
old 4.5.1 ebuilds with new 4.5.2 ones, resulting in blocks.
If this happens to you, please add the offending USE flags (usually
'qt3support' and 'dbus') in your USE= or switch to a desktop profile
(eselect profile list). Check this post [0] for more details on this
issue.
[0] http://www.linuxized.com/p192
root@smoker / #
I have this in my USE flags and I didn't run into this that I recall.
qt3 qt3support qt4
I think they are planning to remove qt3 in the future. I'm not sure how
close that future is tho. I think qt3support is the key here.
Dale
:-) :-)
next prev parent reply other threads:[~2009-10-24 1:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 21:19 [gentoo-user] Uncle: qt-*:4 dependencies/blocks preventing world update Alan E. Davis
2009-10-22 21:28 ` Volker Armin Hemmann
2009-10-23 5:33 ` Dirk Heinrichs
2009-10-24 1:29 ` Alan E. Davis
2009-10-24 1:46 ` Dale [this message]
2009-10-24 23:44 ` Mick
2009-10-25 11:43 ` Amit Dor-Shifer
2009-10-25 12:08 ` Mick
2009-10-25 12:53 ` Amit Dor-Shifer
2009-10-25 13:13 ` Mick
2009-10-25 13:18 ` Alan E. Davis
2009-10-25 14:20 ` Amit Dor-Shifer
2009-10-25 15:45 ` Mick
2009-10-25 12:26 ` Arttu V.
2009-10-26 13:00 ` Alan E. Davis
2009-10-25 12:35 ` econti
2009-10-25 12:49 ` Alan E. Davis
2009-10-25 13:05 ` Alan McKinnon
2009-10-25 13:11 ` Alan E. Davis
2009-10-25 13:23 ` Alan McKinnon
2009-10-25 13:27 ` Alan E. Davis
2009-10-25 17:00 ` Neil Bothwick
2009-10-25 13:26 ` Alan E. Davis
2009-10-25 13:36 ` Alan McKinnon
2009-10-25 13:37 ` Alan McKinnon
2009-10-25 12:58 ` Amit Dor-Shifer
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=4AE25C78.3040008@gmail.com \
--to=rdalek1967@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