From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge on really old tree
Date: Tue, 01 Feb 2011 11:38:41 -0600 [thread overview]
Message-ID: <4D484521.5050404@gmail.com> (raw)
In-Reply-To: <201102010933.49388.alan.mckinnon@gmail.com>
Alan McKinnon wrote:
> Portage can deal with a pure kde-4.5.x to 4.6.0 upgrade, the blockers are all
> soft ones so they just get automagically dealt with.
>
> But kbluetooth has this gem:
>
> COMMON_DEPEND="
> <kde-base/kdelibs-4.6[semantic-desktop?]
> <kde-base/libkworkspace-4.6
> <kde-base/solid-4.6[bluetooth]
> "
>
> Oops. Blocks kdelibs. Basically nothing can proceed but portage doesn't know
> that so it dumps about 300 lines of errors on-screen. And the poor user has to
> sift through all of that to find the root cause. It's there, just hidden right
> in the middle of all the other junk on screen
>
>
Do you have k3b installed? I tried to install it here, it was a blocker
earlier so I -C'd it, and it appears k3b wants a older version of qt
stuff and KDE 4.6 wants the new versions of qt stuff. I have not been
able to work around this yet but would love to know if it is doable yet.
Dale
:-) :-)
next prev parent reply other threads:[~2011-02-01 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 16:35 [gentoo-user] emerge on really old tree Andrei Brezan
2011-01-31 17:22 ` David Abbott
2011-01-31 19:57 ` Alan McKinnon
2011-01-31 22:49 ` Mick
2011-01-31 23:31 ` Alan McKinnon
2011-02-01 7:00 ` Mick
2011-02-01 7:33 ` Alan McKinnon
2011-02-01 17:38 ` Dale [this message]
2011-02-01 18:30 ` Sebastian Beßler
2011-02-01 22:00 ` Dale
2011-02-01 18:46 ` Alan McKinnon
2011-02-01 19:25 ` Dale
2011-02-01 20:58 ` Alan McKinnon
2011-02-01 21:29 ` Dale
2011-02-01 21:50 ` Alan McKinnon
2011-02-01 22:34 ` Dale
2011-02-01 23:56 ` Alan McKinnon
2011-02-02 1:36 ` Peter Humphrey
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=4D484521.5050404@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