| ID | Occurrence | Description | Solution |
|---|---|---|---|
| ID | Occurrence | Description | Solution |
| 1 | [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.14-r2)
[...] [ebuild U ] sys-apps/shadow-4.0.14-r2 [4.0.14-r1] USE="$someuseflags" 0 kB | PAM-login now blocks shadow, because PAM-login was re-merged INTO shadow again. It is safe to remove pam-login. | emerge -Cavt pam-login
|
| 2 | [blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1)
[...] [ebuild N ] sys-libs/libutempter-1.1.2.1 21 kB | Libutempter now replaces utempter. It's safe to unmerge utempter. | emerge -Cavt utempter
|
| 3 | [blocks B ] <media-gfx/gimp-2.2.12 (is blocking app-doc/gimp-help-0.10)
[...] [ebuild U ] media-gfx/gimp-2.2.12 [2.2.11-r1] USE="$someuseflags" 12,573 kB [ebuild N ] app-doc/gimp-help-0.10 USE="$someuseflags" LINGUAS="$somelinguas" 0 kB | GIMP's help was now migrated to an own ebuild called "gimp-help". You have to unmerge the old version of GIMP and after that install the new one of BOTH packages. (Or just GIMP, if you do not want to have the help, too...) | emerge -Cavt gimp
|
| 4 | Deprecated
Got FIXED by removing the old broken versions [blocks B ] ~media-libs/openal-20050504 (is blocking media-libs/freealut-1.1.0) [...] [ebuild N ] media-libs/openal-20050504-r2 USE="$someuseflags" 0 kB [...] [ebuild N ] media-libs/openal-0.0.8 USE="$someuseflags" 850 kB [ebuild N ] media-libs/freealut-1.1.0 451 kB | Deprecated
Got FIXED by removing the old broken versions Due to buggy version numbering of OpenAL, old versions (with "higher" numbers, like 20050504-r1) are being installed over the newest versions (like 0.8.*), even if the dependencies of a program require the newer versions. Masking these old versions will fix the problems. | Deprecated
Got FIXED by removing the old broken versions emerge -Cavt openal
|
| 5 | Update
[blocks B ] kde-base/kde-env (is blocking kde-base/kdelibs-3.5.5-r5) [...] [ebuild U ] kde-base/kdelibs-3.5.5-r5 [3.5.2-r6] [...] | Update
kde-env was merged into kdelibs and is now part of it. You can remove kde-env, emerge the new kdelibs and then use revdep-rebuild to find possibly broken packages. This problem is occurring in the STABLE (x86) tree, too. | emerge -Cavt kde-env
|
| 6 | Deprecated
Got FIXED by removing all the old versions [blocks B ] <sys-apps/dbus-0.62 (is blocking app-emulation/vmware-server-console-1.0.1.29996-r1) [blocks B ] <sys-apps/dbus-0.62 (is blocking app-emulation/vmware-server-1.0.1.29996-r1) [ebuild U ] app-emulation/vmware-server-console-1.0.1.29996-r1 [1.0.1.29996] 0 kB [...] [ebuild U ] app-emulation/vmware-server-1.0.1.29996-r1 [1.0.1.29996] 0 kB | Deprecated
Got FIXED by removing all the old versions Actually, it seems like you have to get the TESTING version of dbus, if you want still to use VMWare Server. Unmask it, emerge it and run a world update. | Deprecated
Got FIXED by removing all the old versions emerge -Cavt dbus
|
| 7 | [blocks B ] <media-sound/esound-0.2.36-r2 (is blocking app-admin/eselect-esd-20060719)
[...] [ebuild U ] media-sound/esound-0.2.36-r2 [0.2.36-r1] USE="$someuseflags" 361 kB [ebuild N ] app-admin/eselect-esd-20060719 1 kB | eselect-esd came bundled with esound 0.2.36-r2. To solve the block issue, simply unmerge esound and run a world update. | emerge -Cavt esound
|
| 9 | Deprecated
Got FIXED by removing all the old versions [blocks B ] <sys-apps/dbus-0.91 (is blocking sys-apps/dbus-1.0.1-r2) [...] [ebuild U ] sys-apps/dbus-1.0.1-r2 [0.62-r1] USE="$someuseflags" 1,373 kB | Deprecated
Got FIXED by removing all the old versions If using ~x86 or having defined ~x86 (TESTING) as the keyword for dbus, you should first unmerge the old 0.* versions of it and then install the newest one. Also, make sure nothing got broken by this update, so run revdep-rebuild, too. | Deprecated
Got FIXED by removing all the old versions emerge -Cavt dbus
|
| 10 | [blocks B ] <dev-python/pygtk-2.9 (is blocking dev-python/pygobject-2.12.3)
[...] [ebuild U ] dev-python/pygtk-2.10.3 [2.8.6] USE="$someuseflags" 2,521 kB [ebuild N ] dev-python/pygobject-2.12.3 USE="$someuseflags" 331 kB | Trivial: to upgrade pyobject, just update pygtk first. | emerge -avt pygtk
|
| 11 | [blocks B ] sys-apps/coldplug (is blocking sys-fs/udev-103)
[...] [ebuild U ] sys-fs/udev-103 USE="$someuseflags" 195,3 kB | Coldplug has been merged into the udev ebuild and is therefore no longer needed as an external installed program.
You can safely unmerge it and then update udev. | emerge -Cavt coldplug
|
| 12 | [blocks B ] dev-php5/pecl-zip (is blocking dev-lang/php-5.2.1-r3)
[...] [ebuild U ] dev-lang/php-5.2.1-r3 [5.1.6-r6] USE="$someuseflags)" 7,019 kB | Currently you cannot use dev-php5/pecl-zip with PHP 5.2.1-r3. Unmerge it and update PHP; update your scripts NOT to make use of pecl-zip. | emerge -Cavt dev-php5/pecl-zip
|
| 13 | [blocks B ] <dev-java/ant-1.7.0 (is blocking dev-java/ant-core-1.7.0)
[blocks B ] <dev-java/ant-tasks-1.7.0 (is blocking dev-java/ant-core-1.7.0) [...] [ebuild U ] dev-java/ant-core-1.7.0 [1.6.5-r14] USE="$someuseflags" 0 kB [ebuild U ] dev-java/ant-tasks-1.7.0-r2 [1.6.5-r3] USE="$someuseflags" 0 kB [ebuild U ] dev-java/ant-1.7.0 [1.6.5] 0 kB | Versions below 1.7.0 of dev-java/ant are blocking the dev-java/ant-core. Also versions below 1.7.0 of dev-java/ant-tasks are blocking the ant core.
This seems to be a little bit tricky. We can not upgrade any of these components, because we would run into the blocking loop again. Thus, we have to remove dev-java/ant and dev-java/ant-tasks first. Just after that we are able to upgrade dev-java/ant-core. Now do not forget to reinstall the removed packages (dev-java/ant and dev-java/ant-tasks). Please be aware, that this will also install a bunch of other little programs due to new dependencies. You should now run a world upgrade. | emerge -Cavt dev-java/ant dev-java/ant-tasks
|
| 14 | [nomerge ] dev-libs/boost-1.34.0 [1.33.1-r1] USE="$someuseflags"
[ebuild N ] dev-util/boost-build-1.34.0 12,717 kB [ebuild U ] dev-libs/boost-1.34.0 [1.33.1-r1] USE="$someuseflags" 0 kB [blocks B ] <dev-libs/boost-1.34.0 (is blocking dev-util/boost-build-1.34.0) | That is rather trivial. We have updates for both boost and boost-build. Although, boost-build-1.34.0 is depending on the newest version of boost, which is, of course, also 1.34.0.
For being able to upgrade both packages, we first have to remove boost and boost-build itself, then re-emerge boost in the newest version and afterwards boost-build. Since boost is a library, that is likely needed by other programs, especially by C++ ones, it is recommended that you first run a world upgrade and then revdep-rebuild to be sure, that all your programs are still compatible with boost (and thus run. :)) | emerge -Cavt boost boost-build
|
| 15 | [ebuild U ] dev-lang/ruby-1.8.6-r1 [1.8.5_p2-r1] USE="$someuseflags" 4,482 kB
[blocks B ] >=dev-lang/ruby-1.8.6 (is blocking dev-ruby/cgi_multipart_eof_fix-1.0.0) | dev-ruby/cgi_multipart_eof_fix-1.0.0 can't coexist with dev-lang/ruby-1.8.6* and higher.
Thus, we simply have to update dev-ruby/cgi_multipart_eof_fix and then update ruby. Everything will be fine after running a world update. | emerge -avt dev-ruby/cgi_multipart_eof_fix
|
| 17 | [ebuild U ] app-text/aspell-0.60.5 [0.50.5-r4] USE="$someuseflags" 1,714 kB
[ebuild U ] app-dicts/aspell-en-6.0.0 [0.51.1] 179 kB [blocks B ] =app-dicts/aspell-en-0.5* (is blocking app-text/aspell-0.60.5) | aspell-en-0.50.x won't work with aspell-0.60.x anymore. The new version is 6.0.0.
We will have to remove aspell-en completely first, upgrade aspell and reinstall aspell-en. After that run a system update to upgrade remaining dictionaries. | emerge -Cavt aspell-en
|
| 18 | [ebuild N ] gnome-base/libgnomekbd-2.18.2 USE="$someuseflags" 352 kB
[ebuild U ] gnome-base/control-center-2.18.1 [2.16.3] USE="$someuseflags" 2,100 kB [ebuild U ] app-text/gnome-doc-utils-0.10.3 [0.8.0] USE="$someuseflags" 442 kB [blocks B ] <gnome-base/control-center-2.17.0 (is blocking gnome-base/libgnomekbd-2.18.2) | You have to remove the old version first in order to install libgnomekbd. | emerge -Cavt gnome-base/control-center
|
| 19 | [ebuild N ] media-libs/libdca-0.0.5 USE="$someuseflags" 385 kB
[...] [blocks B ] media-libs/libdts (is blocking media-libs/libdca-0.0.5) | libdts has been renamed to libdca. So first unmerge media-libs/libdts, after that emerge media-libs/libdca and have a look to the following issue which has to do with VLC and which you might also might hit.
MPlayer can't work with the new libdca yet, so you have to symlink the new libdca.so.0 and libdca.so.0.0.0 to libdts.so.0 and libdts.so.0.0.0 first. Please run ldconfig to update the linker cache. | emerge -Cavt media-libs/libdts
|
| 20 | [ebuild NS ] media-video/vlc-0.9.0_alpha20071009 USE="$someuseflags" 12,361 kB
[...] [blocks B ] <media-video/vlc-0.8.8 (is blocking media-video/vlc-0.9.0_alpha20071009) | Of course, this is also quite trivial.
Unmerge the old version of VLC and emerge the newest one. As you probably also had the previous blocker, run revdep-rebuild to ensure that linking is still fine. You're done. | emerge -Cavt media-video/vlc
|
| 21 | [ebuild NS ] dev-ruby/rails-1.2.5 USE="$someuseflags" 167 kB
[...] ([ebuild U ] dev-lang/ruby-1.8.6_p110-r1 [1.8.5_p2-r1] USE="$someuseflags" 4,657 kB) [...] [blocks B ] <dev-ruby/rails-1.1.6-r1 (is blocking dev-ruby/rails-1.2.5) | That is no rocket science, either.
Uninstall the old rails version, update ruby (as you might have to do it anyways) and install the new rails version. | emerge -Cavt dev-ruby/rails
|
| 22 | [nomerge ] www-apache/mod_perl-2.0.3-r1 [2.0.1-r2] USE="$someuseflags"
[ebuild N ] dev-perl/Apache-Test-1.29 148 kB [ebuild U ] www-apache/mod_perl-2.0.3-r1 [2.0.1-r2] USE="$someuseflags" 3,628 kB [blocks B ] dev-perl/Apache-Test (is blocking www-apache/mod_perl-2.0.1-r2) | It seems like older versions www-apache/mod_perl are blocking dev-perl/Apache-Test.
Thus you have to unmerge the old version of www-apache/mod_perl and after that install the new one, which will automagically fetch Apache-Test as a dependency. It is now recommended to run a world update, because it is likely that also other apache related packages need an upgrade. | emerge -Cavt www-apache/mod_perl
|
| 23 | [ebuild U ] app-crypt/gnupg-2.0.7 [1.4.7-r1] USE="$someuseflags" LINGUAS="$somelinguas" 3,526 kB
[...] [blocks B ] <=app-crypt/gnupg-2.0.1 (is blocking app-crypt/gnupg-2.0.7) | Older versions (1.x) of GNUPG are blocking the newest 2.x line.
Thus remove app-crypt/gnupg first, make sure that no other version is installed anymore and then install the newest version. It is recommended to run revep-rebuild. | emerge -Cavt app-crypt/gnupg
|
| 24 | [nomerge ] dev-libs/boost-1.34.1-r2 [1.33.1-r1] USE="$someuseflags"
[ebuild N ] dev-util/boost-build-1.34.1 12,683 kB [ebuild U ] dev-libs/boost-1.34.1-r2 [1.33.1-r1] USE="$someuseflags" 6 kB [...] [blocks B ] <dev-libs/boost-1.34.0 (is blocking dev-util/boost-build-1.34.1) | Versions prior to 1.34.0 of dev-libs/boost are blocking dev-util/boost-build. Thus, we need to unmerge the old boost version first and install the newest one (which will of course also automagically pull in boost-build as a dependency.)
Please, please remember to run revdep-rebuild, because boost is a fairly system critical package and a broken configuration or not updated files might cause big trouble. | emerge -Cavt dev-libs/boost
|
| 25 | [ebuild U ] app-accessibility/speech-tools-1.2.96_beta [1.2.95_beta-r1] USE="$someuseflags" 1,246 kB
[ebuild U ] app-accessibility/festival-1.96_beta [1.95_beta-r4] USE="$someuseflags" 15,893 kB [...] [blocks B ] <app-accessibility/festival-1.96_beta (is blocking app-accessibility/speech-tools-1.2.96_beta) | Same procedure as every time, please remove the old version of app-accessibility/festival prior installing app-accessibility/speech-tools.
I want to thank zifix nochoans, who discovered this. Lately I have been not syncing/updating much, but here you are finally. :) | emerge -Cavt app-accessibility/festival
|
| 26 | [...]
[ebuild UD] media-libs/gst-plugins-base-0.10.14 [0.10.15] USE="$someuseflags" 1,588 kB [ebuild U ] x11-themes/gnome-themes-2.20.2 [2.20.1] USE="$someuseflags" 2,347 kB [ebuild UD] media-libs/gstreamer-0.10.14 [0.10.15] USE="$someuseflags" 1,958 kB [ebuild U ] media-plugins/gst-plugins-vorbis-0.10.17 [0.10.15] 0 kB [ebuild U ] media-plugins/gst-plugins-ogg-0.10.17 [0.10.15] 0 kB [ebuild U ] media-libs/gst-plugins-base-0.10.17 [0.10.15] USE="$someuseflags" 0 kB [ebuild U ] media-libs/gstreamer-0.10.17 [0.10.15] USE="$someuseflags" 2,118 kB [...] [blocks B ] <media-libs/gst-plugins-ugly-0.10.6-r1 (is blocking media-libs/gstreamer-0.10.17) | The usual "deinstall, install" approach doesn't work here. ;)
However, you most probably see this message, because you are using the ~arch media-libs/gstreamer package, but did not unmask media-libs/gst-plugins-ugly. This time, simply adding dev-libs/gst-plugins-ugly ~x86 to your /etc/portage/package.keywords file will do the trick. Then remove media-libs/gst-plugins-ugly and reinstall it (in the newest version.) After that you can simply rerun the update process and the block should be gone. | echo "media-libs/gst-plugins-ugly ~x86" >> /etc/portage/package.keywords
|
| 27 | [ebuild N ] app-admin/eselect-wxwidgets-0.7-r1 0 kB
[ebuild NS ] x11-libs/wxGTK-2.8.7.1-r1 USE="$someuseflags" 25,745 kB [blocks B ] <=x11-libs/wxGTK-2.6.4.0-r2 (is blocking app-admin/eselect-wxwidgets-0.7-r1) | Like everytime, please your wxGTK version is too old for the new eselect (which will enable you to switch between wxGTK 2.6 and wxGTK 2.8. :))
The oldest working version with eselect-wxwidgets is 2.6.4.0-r3, thus we will have to update wxGTK first. After that you can install the new eselect-wxwidgets (but preferably using -1 or --oneshot for not adding it to your world file, since it neither would have been added automagically.) Due to this rather critical update, it is recommended to run revdep-rebuild. | emerge -uavt --nodeps x11-libs/wxGTK
|
| 28 | [ebuild NS ] x11-libs/openmotif-2.3.0 USE="$someuseflags" 9,626 kB
[ebuild U ] x11-libs/motif-config-0.10-r2 [0.9-r1] 9 kB [...] [blocks B ] <x11-libs/openmotif-2.3.0 (is blocking x11-libs/motif-config-0.10-r2) | Although the new motif version is added as a new slot (but I do not see any logic behind this, either), older versions are blocking motif-config.
No rocket science, the usual approach will do it. After this you might want to run revdep-rebuild. | emerge -Cavt x11-libs/motif-config
|
| 29 | [ebuild U ] sys-apps/coreutils-6.10-r1 [6.9-r1] USE="$someuseflags" 3,670 kB
[...] [blocks B ] >=sys-apps/coreutils-6.10 (is blocking sys-apps/mktemp-1.5) [blocks B ] sys-apps/mktemp (is blocking sys-apps/coreutils-6.10-r1) | UPDATE
This block will as of now also hit arch users! mktemp has been merged into coreutils and thus is obsolete for now. So, if you plan to upgrade coreutils, unmerge mktemp first. After that please make sure to update your coreutils. :) (Be prepared for multiple depencies.) | emerge -Cavt sys-apps/mktemp
|
| 30 | [...]
[ebuild N ] dev-util/gtk-doc-am-1.10-r1 395 kB [ebuild U ] dev-util/gtk-doc-1.10-r1 [1.8-r2] USE="$someuseflags" 0 kB [...] [blocks B ] dev-util/gtk-doc-am (is blocking dev-util/gtk-doc-1.8-r2) [blocks B ] <=dev-util/gtk-doc-1.10 (is blocking dev-util/gtk-doc-am-1.10-r1) | dev-util/gtk-doc-am is a new package and a dependency for dev-util/gtk-doc.
However, you will not be able to install dev-util/gtk-doc-am, if your dev-util/gtk-doc is too old. Thus please update dev-util/gtk-doc and proceed in updating your system. | emerge -Cav dev-util/gtk-doc
|
| 31 | [...]
[ebuild N ] virtual/latex-base-1.0 0 kB [ebuild N ] dev-texlive/texlive-latexrecommended-2007 USE="$someuseflags" 22,731 kB [ebuild N ] dev-texlive/texlive-latex-2007 USE="$someuseflags" 29,960 kB [ebuild N ] dev-texlive/texlive-basic-2007 USE="$someuseflags" 29,249 kB [ebuild N ] dev-texlive/texlive-documentation-base-2007 USE="$someuseflags" 1,017 kB [...] [ebuild N ] app-text/tetex-3.0_p1-r6 USE="$someuseflags" 102,314 kB [...] [nomerge ] dev-texlive/texlive-latexrecommended-2007 USE="$someuseflags" [ebuild N ] app-text/texlive-core-2007-r12 USE="$someuseflags" 42,232 kB [...] [blocks B ] app-text/tetex (is blocking app-text/texlive-core-2007-r12) | app-text/tetex is now deprecated and replaced by the texlive-* ebuilds.
To solve this block you have to unmerge app-text/tetex and install the new virtual package virtual/latex-base which will automatically depend on the new eBuilds. Please make sure to read The Latex upgrade guide for Gentoo as well. | emerge -Cav app-text/tetex
|
| 32 | [...]
[nomerge ] dev-lang/python-2.5.2-r5 USE="$someuseflags" [ebuild U ] app-admin/python-updater-0.5 [0.2] 6 kB [ebuild NS ] dev-python/python-docs-2.5.1 1,589 kB [blocks B ] <dev-lang/python-2.3.6-r2 (is blocking app-admin/python-updater-0.5, app-admin/python-updater-0.2) | The older, say 2.3.x, versions of dev-lang/python have been hard masked in portage due to the lack of maintenance by Gentoo and Python Developers.
Versions 2.4.x are currently stable and 2.5.x might become stable soon, so either way, you will not need Python 2.3 anymore. Simply remove the old packages and re-run your world update. | emerge -Cav "<dev-lang/python-2.4" (remember to either quote the whole string, or to escape the "<" only.)
|
| 33 | [...]
[ebuild N ] gnome-base/gnome-settings-daemon-2.22.2.1 USE="$someuseflags" 1,113 kB [ebuild U ] gnome-base/gnome-control-center-2.22.2.1 [2.20.3] USE="$someuseflags" 2,061 kB [ebuild U ] gnome-base/gnome-panel-2.22.2 [2.20.3] USE="$someuseflags" 3,179 kB [ebuild N ] dev-libs/libgweather-2.22.3 USE="$someuseflags" 6,123 kB [ebuild U ] gnome-base/gnome-applets-2.22.3 [2.20.1] USE="$someuseflags" 7,333 kB [...] [ebuild N ] dev-libs/totem-pl-parser-2.22.3 USE="$someuseflags" 812 kB [ebuild U ] media-video/totem-2.22.2-r1 [2.20.3] USE="$someuseflags" 2,348 kB [...] [blocks B ] <media-video/totem-2.21 (is blocking dev-libs/totem-pl-parser-2.22.3) [blocks B ] <gnome-base/gnome-applets-2.22.0 (is blocking dev-libs/libgweather-2.22.3) [blocks B ] <gnome-base/gnome-control-center-2.22 (is blocking gnome-base/gnome-settings-daemon-2.22.2.1) | Various packages need updating, before their new dependencies will be able to be merged. Thus, quick-updating these packages will fix the blocks.
After that you will be able to resume your world update. | emerge -Cav media-video/totem
|
| 34 | [...]
[nomerge ] app-crypt/qca-tls-1.0-r3 [?] [ebuild NS ] app-crypt/qca-2.0.0-r2 USE="$someuseflags" 4,987 kB [...] [blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) | Older versions of app-crypt/qca are blocking newer ones.
Please unmerge the old app-crypt/qca version first and install the new version afterwards. Additionally, you can now continue to upgrade your system. | emerge -Cavt app-crypt/qca
|
| 35 | [...]
[ebuild U ] app-crypt/mit-krb5-1.6.3-r4 [1.6.3-r1] USE="$someuseflags" 11,636 kB [ebuild N ] sys-libs/e2fsprogs-libs-1.41.2 USE="$someuseflags" 479 kB [nomerge ] sys-apps/util-linux-2.13.1.1 USE="$someuseflags" [ebuild U ] sys-fs/e2fsprogs-1.41.2 [1.40.9] USE="$someuseflags" 4,263 kB [...] [blocks B ] sys-libs/e2fsprogs-libs (is blocking sys-libs/com_err-1.40.9, sys-libs/ss-1.40.9) [blocks B ] <sys-fs/e2fsprogs-1.41 (is blocking sys-libs/e2fsprogs-libs-1.41.2) [blocks B ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.2) [blocks B ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.2) | NFS USERS Please temporarly disable any mounts for /usr/portage/distfiles (directories mounted with --bind are still OK.) Unmount /usr/portage/distfiles and create it as a normal directory, if needed. Your upgrade will fail otherwise!
sys-libs/ss and sys-libs/com_err have been merged into a new package, called sys-libs/e2fsprogs-libs. Thus, you can remove the old packages sys-libs/ss and sys-libs/com_err. But first make sure to download the sources for the new package sys-libs/e2fsprogs-libs. wget will not work anymore after uninstalling sys-libs/com_err. sys-fs/e2fsprogs is being uninstalled because you will otherwise experience file collisions with the new package sys-libs/e2fsprogs-libs. Afterwards just install the new package sys-libs/e2fsprogs-libs and reinstall the sys-fs/e2fsprogs package. Order matters. As you probably were on your way through a system update, continue it now. Lastly, please run revdep-rebuild to find any dynamic linking inconsistencies. | emerge -fv sys-libs/e2fsprogs-libs sys-fs/e2fsprogs
|
| 36 | [...]
[ebuild U ] x11-drivers/xf86-input-keyboard-1.3.2 [1.1.1] USE="$someuseflags" 264 kB [?=>0] [ebuild U ] x11-drivers/xf86-input-mouse-1.4.0 [1.2.3] USE="$someuseflags" 286 kB [0] [ebuild U ] x11-drivers/xf86-video-fbdev-0.4.0 [0.3.1] USE="$someuseflags" 237 kB [?=>0] [ebuild U ] x11-drivers/xf86-video-nv-2.1.12 [2.1.9] USE="$someuseflags" 380 kB [0] [ebuild U ] x11-drivers/xf86-video-vesa-2.2.0 [1.3.0] USE="$someuseflags" 243 kB [?=>0] [ebuild U ] x11-base/xorg-server-1.5.3-r5 [1.3.0.0-r6] USE="$someuseflags" INPUT_DEVICES="$someinputdevices" \ VIDEO_CARDS="$somevideocards" 5,546 kB [0] [ebuild U ] x11-apps/xinit-1.0.8-r4 [1.0.5-r1] USE="$someuseflags" 115 kB [0] [...] [ebuild U ] x11-misc/xkeyboard-config-1.5 [1.1] 559 kB [0] [...] [nomerge ] x11-base/xorg-server-1.5.3-r5 [1.3.0.0-r6] USE="$someuseflags" INPUT_DEVICES="$someinputdevices" \ VIDEO_CARDS="$somevideocards" [0] [ebuild N ] x11-libs/libpciaccess-0.10.5 USE="$someuseflags" 255 kB [0] [...] [blocks B ] <x11-base/xorg-server-1.5 ("<x11-base/xorg-server-1.5" is blocking x11-libs/libpciaccess-0.10.5) | Due to the upgrade from Xorg Server 1.3 or 1.4 to 1.5, a new library is required which in turn does conflict with the old Xorg Server version.
To solve this block, backup your current xorg-server version first (binpkg) and re-emerge the newest version afterwards. Not backupping the old version may lead to big problems when neither the new, nor the old package can be compiled! Afterwards please proceed to update the rest of your system, particularly of course the X subsystem. It is recommended to run revdep-rebuild to check for broken libraries. | quickpkg x11-base/xorg-server
|
| 37 | [nomerge ] media-video/istanbul-0.2.2 USE="$someuseflags" [0]
[nomerge ] dev-python/gnome-python-extras-2.19.1-r3 [2.19.1-r2] USE="$someuseflags" [0] [nomerge ] dev-python/egg-python-2.19.1 USE="$someuseflags" [0] [uninstall ] dev-python/gnome-python-extras-2.19.1-r2 USE="$someuseflags" [0] [...] [ebuild U ] dev-python/gnome-python-extras-2.19.1-r3 [2.19.1-r2] USE="$someuseflags" 0 kB [0] [...] [ebuild N ] dev-python/gdl-python-2.19.1 USE="$someuseflags" 356 kB [0] [ebuild U ] dev-libs/gdl-2.24.0 [0.7.6] USE="$someuseflags" 539 kB [0] [ebuild N ] dev-python/libgda-python-2.19.1 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/gtkmozembed-python-2.19.1-r11 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/egg-python-2.19.1 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/gtkspell-python-2.19.1 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/gtkhtml-python-2.19.1 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/libgksu-python-2.19.1 USE="$someuseflags" 0 kB [0] [ebuild N ] dev-python/gnome-python-extras-base-2.19.1 USE="$someuseflags" 0 kB [0] [...] [blocks B ] <=dev-python/gnome-python-extras-2.19.1-r2 ("<=dev-python/gnome-python-extras-2.19.1-r2" is blocking \ dev-python/libgksu-python-2.19.1, dev-python/gnome-python-extras-base-2.19.1, \ dev-python/gdl-python-2.19.1, dev-python/egg-python-2.19.1, \ dev-python/gtkhtml-python-2.19.1, dev-python/libgda-python-2.19.1, \ dev-libs/gdl-2.24.0, dev-python/gtkspell-python-2.19.1) [...] [blocks B ] <=dev-python/gnome-python-extras-2.19.1-r2 ("<=dev-python/gnome-python-extras-2.19.1-r2" is blocking \ dev-python/libgksu-python-2.19.1, dev-python/gnome-python-extras-base-2.19.1, \ dev-python/gdl-python-2.19.1, dev-python/egg-python-2.19.1, \ dev-python/gtkhtml-python-2.19.1, dev-python/libgda-python-2.19.1, \ dev-libs/gdl-2.24.0, dev-python/gtkspell-python-2.19.1) [blocks B ] <=dev-python/gnome-python-extras-2.19.1-r2 \ ("<=dev-python/gnome-python-extras-2.19.1-r2" is blocking \ dev-python/gtkmozembed-python-2.19.1-r11) [blocks B ] <dev-python/gdl-python-2.19.1-r1 ("<dev-python/gdl-python-2.19.1-r1" is \ blocking dev-libs/gdl-2.24.0) | A newer version of dev-python/gnome-python-extras is required to enjoy all the new python-gtk packages.
Although emerge wants to unmerge the old version, there still seems to be a blocking condition. This blocking condition is also due to dev-python/gdl-python-2.19.1-r1 being still ~x86'd. In order to resolve this block, please add a keyword for this very version. Afterwards please unmerge the old version of dev-python/gnome-python-extras and update your dev-python/gnome-python package. The blocking problem should now be solved. Then just resume the update procedure. | echo "<=dev-python/gdl-python-2.19.1-r1 ~x86" >> /etc/portage/package.keywords
|
| 38 | [nomerge ] media-libs/gst-plugins-base-0.10.22 [0.10.21] USE="$someuseflags" [0]
[uninstall ] media-libs/gst-plugins-bad-0.10.9 USE="$someuseflags" [0] [...] [blocks b ] <media-libs/gst-plugins-bad-0.10.11 ("<media-libs/gst-plugins-bad-0.10.11" is blocking media-libs/gst-plugins-ugly-0.10.11) [blocks b ] <media-libs/gst-plugins-bad-0.10.10 ("<media-libs/gst-plugins-bad-0.10.10" is blocking media-libs/gst-plugins-base-0.10.22) [ebuild U ] media-libs/gst-plugins-bad-0.10.11 [0.10.9] USE="$someuseflags" 2,505 kB [0] [...] [blocks B ] <media-libs/gst-plugins-bad-0.10.10 ("<media-libs/gst-plugins-bad-0.10.10" is blocking media-libs/gst-plugins-base-0.10.22) | THIS BLOCK DOES ONLY APPLY TO ~x86 USERS CURRENTLY!
Older versions of media-libs/gst-plugins-bad block the other newer gstreamer plugins. Please just try to update media-libs/gst-plugins-bad semi-manually; newer portage versions will automatically uninstall the old version and upgrade to the newest one. Eventually the world upgrade should work without any gstreamer package blocks. | emerge -1uDavt media-libs/gst-plugins-bad
|
| 39 | [nomerge ] app-shells/bash-completion-1.0-r3 [0.20081219-r1] [0]
[uninstall ] games-misc/cowsay-3.03-r1 USE="$someuseflags" [0] [...] [ebuild U ] games-misc/cowsay-3.03-r2 [3.03-r1] USE="$someuseflags" 0 kB [0] [...] [blocks B ] <=games-misc/cowsay-3.03-r1 ("<=games-misc/cowsay-3.03-r1" is blocking app-shells/bash-completion-1.0-r3) | Trivial update.
You must first use the ~x86 keyword on cowsay to unmask the new version. Then just update games-misc/cowsay. After that resume your world update. | echo "<=games-misc/cowsay-3.03-r2 ~x86" >> /etc/portage/package.keywords
|
| 40 | [ebuild U ] app-mobilephone/gammu-1.24.0-r1 [1.22.1-r2] USE="$someuseflags" LINGUAS="$somelinguas" 1,776 kB [0]
[...] [blocks B ] dev-python/python-gammu ("dev-python/python-gammu" is blocking app-mobilephone/gammu-1.24.0-r1) | It seems like dev-python/python-gammu is not needed anymore for never versions of app-mobilephone/gammu. Thus is should be removed from the system.
Just unmerge it and procede with the world update. | emerge -Cavt dev-python/python-gammu
|