This is probably going to kill my desktop, that relies on Xorg 1.7 that requires hal.
In fact, hal is running right now.
I'm pretty worried about openrc, too.
Let's see if I can manage this upgrade. I'll let you know.

(x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-qt3support-4.8.2[accessibility=,aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-declarative-4.8.2::gentoo, ebuild scheduled for merge)
>=x11-libs/qt-qt3support-4.8.0:4[accessibility] required by (kde-base/khelpcenter-4.9.3::gentoo, ebuild scheduled for merge)
(and 7 more with the same problems)

x11-libs/qt-gui:4

(x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-gui-4.8.2[aqua=,c++0x=,debug=,glib=,qpa=,qt3support] required by (x11-libs/qt-core-4.8.2::gentoo, ebuild scheduled for merge)
>=x11-libs/qt-gui-4.8.0:4[accessibility,dbus] required by (kde-base/kdelibs-4.9.3::gentoo, ebuild scheduled for merge)
(and 12 more with the same problems)

(x11-libs/qt-gui-4.6.2::gentoo, installed) pulled in by
~x11-libs/qt-gui-4.6.2[accessibility=,aqua=,debug=,qt3support] required by (x11-libs/qt-qt3support-4.6.2::gentoo, installed)
(and 1 more with the same problem)

x11-libs/qt-dbus:4

(x11-libs/qt-dbus-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/qt-dbus-4.8.0:4 required by (kde-base/kdelibs-4.9.3::gentoo, ebuild scheduled for merge)
~x11-libs/qt-dbus-4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)
(and 6 more with the same problems)

(x11-libs/qt-dbus-4.6.2::gentoo, installed) pulled in by
~x11-libs/qt-dbus-4.6.2[aqua=,debug=] required by (x11-libs/qt-gui-4.6.2::gentoo, installed)

x11-libs/qt-core:4

(x11-libs/qt-core-4.6.2-r1::gentoo, installed) pulled in by
~x11-libs/qt-core-4.6.2[aqua=,debug=] required by (x11-libs/qt-script-4.6.2::gentoo, installed)
(and 4 more with the same problem)

(x11-libs/qt-core-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/qt-core-4.8.0:4[qt3support,ssl] required by (kde-base/nepomuk-core-4.9.3::gentoo, ebuild scheduled for merge)
~x11-libs/qt-core-4.8.2[aqua=,debug=,ssl,qpa=] required by (x11-libs/qt-webkit-4.8.2::gentoo, ebuild scheduled for merge)
(and 17 more with the same problems)

x11-libs/qt-script:4

(x11-libs/qt-script-4.6.2::gentoo, installed) pulled in by
~x11-libs/qt-script-4.6.2[aqua=,debug=] required by (x11-libs/qt-gui-4.6.2::gentoo, installed)

(x11-libs/qt-script-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/qt-script-4.8.0:4 required by (kde-base/katepart-4.9.3::gentoo, ebuild scheduled for merge)
~x11-libs/qt-script-4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-declarative-4.8.2::gentoo, ebuild scheduled for merge)
(and 7 more with the same problems)

(x11-libs/qt-sql-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/qt-sql-4.8.0:4[qt3support] required by (kde-base/kdesu-4.9.3::gentoo, ebuild scheduled for merge)
~x11-libs/qt-sql-4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support=] required by (x11-libs/qt-declarative-4.8.2::gentoo, ebuild scheduled for merge)
(and 7 more with the same problems)

media-libs/libpng:0

(media-libs/libpng-1.5.13-r1::gentoo, ebuild scheduled for merge) pulled in by
>=media-libs/libpng-1.4.3:0 required by (net-print/cups-1.5.2-r4::gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

(media-libs/libpng-1.2.43-r2::gentoo, installed) pulled in by
=media-libs/libpng-1.2* required by (x11-apps/xcursorgen-1.0.3::gentoo, installed)

x11-libs/xcb-util:0

(x11-libs/xcb-util-0.3.6::gentoo, installed) pulled in by
<x11-libs/xcb-util-0.3.8 required by (x11-libs/startup-notification-0.10::gentoo, installed)

(x11-libs/xcb-util-0.3.9::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/xcb-util-0.3.9 required by (x11-libs/xcb-util-wm-0.3.9::gentoo, ebuild scheduled for merge)
(and 3 more with the same problem)

media-libs/phonon:0

(media-libs/phonon-4.6.0-r1::gentoo, ebuild scheduled for merge) pulled in by
>=media-libs/phonon-4.6.0 required by (media-libs/phonon-gstreamer-4.6.2-r1::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

(media-libs/phonon-4.3.80-r1::gentoo, installed) pulled in by
media-libs/phonon[xine?] required by (kde-base/phonon-kde-4.3.5::gentoo, installed)

media-libs/alsa-lib:0

(media-libs/alsa-lib-1.0.21a::gentoo, installed) pulled in by
media-libs/alsa-lib[alsa_pcm_plugins_extplug,alsa_pcm_plugins_ioplug] required by (net-wireless/bluez-4.63::gentoo, installed)

(media-libs/alsa-lib-1.0.25-r1::gentoo, ebuild scheduled for merge) pulled in by
>=media-libs/alsa-lib-1.0.25 required by (media-sound/alsa-utils-1.0.25-r1::gentoo, ebuild scheduled for merge)

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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

The following USE changes are necessary to proceed:
#required by dev-db/virtuoso-server-6.1.6, required by dev-libs/soprano-2.8.0[virtuoso], required by kde-base/nepomuk-core-4.9.3, required by kde-base/kdelibs-4.9.3[semantic-desktop], required by sys-auth/polkit-kde-agent-0.99.0, required by kde-misc/polkit-kde-kcmodules-0.98_pre20120917
>=sys-libs/zlib-1.2.7 minizip

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

The following USE changes are necessary to proceed:
#required by dev-db/virtuoso-server-6.1.6, required by dev-libs/soprano-2.8.0[virtuoso], required by app-office/akonadi-server-1.8.1, required by kde-base/kdepim-runtime-4.9.3, required by kde-base/kdepim-common-libs-4.9.3, required by kde-base/korganizer-4.9.3, required by kde-base/kmail-4.9.3, required by @selected, required by @world (argument)
>=sys-libs/zlib-1.2.7 minizip

emerge: there are no ebuilds to satisfy "x11-libs/wxGTK:2.6".
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

emerge: there are no ebuilds to satisfy "sys-apps/slocate".
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

I unmerged slocate and wxGTK2:6 (forgot why they were in world).
Then I added
sys-libs/zlib minizip
to package.use
Finally I ran
emerge --unmerge talloc ghostscript-gpl gnu-gs-fonts-std
and now I'm emerging -e world.
It will compile for days (1/802 now !!).

Bravo, you did good work, for some reason several replies you posted did not tickle my email; else I would have suffered with you.
slocate sped up searches and was replaced by mlocate a year or two or three ago. recommend emerge mlocate after a few days of emerge -e _________________Defund the FCC.

I have to say I'd have reinstalled. But since you're underway, well done. I hope you're not using the machine at the same time? You should be doing the upgrades in a console login, with xdm not started at all.

I'd do -e system before you went near world. Then do xorg-server, and build up from there, same as with a new install. In fact, treat it exactly like a new install, so you can do: USE='-X' emerge -e system first. Then you'll probably need to emerge -1 xorg-server and x11-drivers (without -e) and then try -e system again, this time without USE='-X' in front of it.

To upgrade only installed x11-drivers, use: emerge -1 $(qlist -IC x11-drivers/) (q is from portage-utils which I'd upgrade immediately if you already use it.) Or you can just do

Code:

ls /var/db/pkg/x11-drivers/

to see what you have installed.

(No need to use -e from here on.)
Then move on to Qt, and finally kde-libs if you're running it. Only then approach world, but I'd advise doing it in pieces, by going for specific apps you use, or their dependencies (you should be using emerge -1 for all of this, as you don't want to add anything to world.) You may also need to disable some USE flags earlier on to get a slim set of dependencies built, and reenable them later once those are in place (similar to disabling X for system, but you'll likely find it easier to edit make.conf along the way.)

After you've upgraded, you should move make.conf to /etc/portage/make.conf.

Since emerge world is going on, I will let it go.
Of course, X is not running, I'm writing from another machine.
I stopped hal before start, and I'm running the update from an ssh shell, jusl to be able to copy/paste in the forum.
I didn't know the trick USE "-x" emerge. Thank you.
I hope portage knows what it's doing (emerging X11-libs/qt-core-4.82 right now, 195/802). Let's see tomorrow.

Emerge stopped over qt-webkit with compilation issues.
I took the chance to verify openrc migration as suggested by donahue, and everything looks ok.
OpenRC installed and baselayout updated to 2.1-r1.
I ran dispathc-conf, removed rc, env-updated and reboot.
I have a wrong keymap, some warning about opts variable (maybe something auto-starting is not updated), but important things worked.

I wonder if I have to run USE="-X -kde".
I will check a while about the compilation error, then I will take a decision on how to proceed.

As usual, any help appreciated.

Edit.: I double-checked portage is up-to-date, and tried -X -kde, found real-lpath blocking. This leads to me to upgrade eselect and gentoolkit. These, like patch, shouldn't be updated earlier by the system? ...Got it: portage-utils, SteveL.

Emerge stopped over qt-webkit with compilation issues.
I took the chance to verify openrc migration as suggested by donahue, and everything looks ok.
OpenRC installed and baselayout updated to 2.1-r1.
I ran dispathc-conf, removed rc, env-updated and reboot.
I have a wrong keymap, some warning about opts variable (maybe something auto-starting is not updated), but important things worked.

I wonder if I have to run USE="-X -kde".
I will check a while about the compilation error, then I will take a decision on how to proceed.

As usual, any help appreciated.

Edit.: I double-checked portage is up-to-date, and tried -X -kde, found real-lpath blocking. This leads to me to upgrade eselect and gentoolkit. These, like patch, shouldn't be updated earlier by the system? ...Got it: portage-utils, SteveL.

Now running USE="-X -kde -qt4" emerge -e system

remove kde-base/plasma-workspace-4.7.1 and kde-base/kcontrol-4.4.50.
see if either realpath or coreutils needs updating.

for future reference, to avoid this issues, keep your system updated as possible._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

gentoo is a rolling distribution, and upgrades should happen in a weekly to monthly interval to avoid certain complications.
Yes, it is perfectly possible to upgrade a 2-year-old installation, but usually rather painful and needs a look of handy work.

V._________________read the portage output!
If my answer is too concise, ask for an explanation.

for future reference, to avoid this issues, keep your system updated as possible

I don't believe you really said this.

I did, I don't think I've said anything wrong, in fact, following this advice from the beginning would have prevented getting into the mess you're in now.

I see enough gentoo users that don't comprehend what gentoo is all about and that usually results in issues like you have.

regardless, I apologize if I've offended you in any possible way, it was not my intentions._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

The problem is that I'm very n00b to handle this kind of upgrade, but probably this experience will help me someway.
One thing I understood, for example, is that it's very important to emerge -1 packets to avoid them enter in world collection.

Now I'm fighting to get this X11-libs/qt-webkit compiled.
The problem is:

Code:

gst/interfaces/streamvolume.h: No such file or directory

Maybe SteveL or one of you veteran guys can explain me how to emerge -e system without suffering for X11-libs problems,
Maybe I have to unmerge X11-* and emerge them after system is up2date.
In other words, reduce world to a minimal package list and then continue like a fresh install.
Doing so, I will loose email settings, firefox bookmarks and other stuff like that?

I will do that as soon as I can.
I checked /usr/include/gstreamer-0.10/gst/interfaces, not finding the missing file.
Now I'm trying to upgrade gstreamer (emerge -1uDN gstreamer).
It pulled in 54 packages now emerging.
I hope I didn't break something (python 2.7 and 3.4(I think) are now in).
Lot of medium-level stuff now upgraded (sed, bash, make, etc.)

The question is always, how I can upgrade sytem non-X stuff before facing X11 and Xorg, as SteveL suggested?
I tried with USE='-X -kde -qt4' without luck.

I will do that as soon as I can.
I checked /usr/include/gstreamer-0.10/gst/interfaces, not finding the missing file.
Now I'm trying to upgrade gstreamer (emerge -1uDN gstreamer).
It pulled in 54 packages now emerging.
I hope I didn't break something (python 2.7 and 3.4(I think) are now in).
Lot of medium-level stuff now upgraded (sed, bash, make, etc.)

The question is always, how I can upgrade sytem non-X stuff before facing X11 and Xorg, as SteveL suggested?
I tried with USE='-X -kde -qt4' without luck.

I think that there are pkgs which depends on either one of the pkgs you try to block, so the only way is to pinpoint them an unmerge them._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

emerge --keep-going -eav system will rebuild the tool chain skipping past any packages that fail to compile. A list of the failed packages is presented at the end of the run. The failed packages can then be dealt with individually or as a group without redoing every package in system, e.g. emerge -1 qt-webkit.
emerge -uND --keep-going system to update
emerge --keep-going -eav world
emerge --keep-going -uND world_________________Defund the FCC.