From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kde update
Date: Mon, 30 May 2011 18:16:44 +0100 [thread overview]
Message-ID: <201105301816.55061.michaelkintzios@gmail.com> (raw)
In-Reply-To: <881505824.2229441306773917747.JavaMail.root@spooler5n-g27.priv.proxad.net>
[-- Attachment #1: Type: Text/Plain, Size: 1783 bytes --]
On Monday 30 May 2011 17:45:17 Alain DIDIERJEAN wrote:
> Trying to update from kde4.5 to kde4.6
> A simple "emerge -uD world" gives:
>
> [ebuild U ] x11-libs/qt-core-4.7.2-r1 [4.6.3-r1] USE="-jit%
> -private-headers%" [ebuild U ] x11-libs/qt-sql-4.7.2 [4.6.3-r2]
> [blocks b ] <x11-libs/qt-sql-4.7.2 ("<x11-libs/qt-sql-4.7.2" is
> blocking x11-libs/qt-test-4.7.2, x11-libs/qt-svg-4.7.2,
[snip ...]
> (and 13 more)
>
>
> All together 982 lines as above.
> Besides that, gentoo amd64 works fine on my box and I emerge everyday
> packages to upgrade, except those which are kde's. Questions:
> - what the hell is this mess, did I do something wrong ?
No, nothing wrong, new packages that the latest qt and kde4.6 want are being
blocked by packages already installed.
> - have any of you got the same kind of troubles ?
Yes, I did on 3 different boxen.
> - is there a way to go back to an up to date clean install, I mean besides
> reinstalling from scratch or going for Ubuntu ? Reasons that make me go
> for gentoo 8 or 9 years ago:
> - excellent docs. (as of to-day, some docs need updating);
> - easyness of maintenance, no need for periodical reinstall (I'm not sure
> this time); - stable packages are renewed in time, not too soon, not too
> late; - portage works like a charm.
> Hope I can get some help
Don't panic! What I did was to progressively uninstall the blockers and then
run emerge -uaDv world. Eventually there were no blockers, the latest qt was
installed and then kde4.6.
Everything now is like a "clean new install" should be.
If you're running 2.2 portage there may be some automagic way of achieving
this, but with portage-2.1.9.42 I had to do it manually.
HTH.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-30 17:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 16:45 [gentoo-user] kde update Alain DIDIERJEAN
2011-05-30 17:16 ` Mick [this message]
2011-05-30 19:02 ` Neil Bothwick
2011-05-30 19:11 ` Mick
2011-05-30 20:04 ` Dale
2011-05-31 15:11 ` Paul Hartman
2011-05-31 15:27 ` Mark Knecht
2011-05-31 19:07 ` Alan McKinnon
2011-05-31 20:00 ` Dale
2011-05-31 20:20 ` Nils Larsson
2011-05-31 21:13 ` Dale
2011-05-31 21:32 ` Alan McKinnon
2011-05-31 21:55 ` Dale
2011-05-31 22:02 ` Alan McKinnon
2011-05-31 22:35 ` Dale
2011-05-31 23:30 ` Alan McKinnon
2011-05-31 23:49 ` Peter Humphrey
2011-06-01 0:11 ` Dale
2011-05-31 20:35 ` Alan McKinnon
2011-06-02 14:32 ` [gentoo-user] kde update: SOLVED Alain DIDIERJEAN
2011-06-02 15:44 ` Mick
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=201105301816.55061.michaelkintzios@gmail.com \
--to=michaelkintzios@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