On Tuesday 23 September 2008 12:57:24 econti wrote: > Hi all, to-day I upgraded my portage and then I ran > emerge -NDpvu here is the output: > > [ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc > -test" 4,397 kB > [ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X > -nsplugin" 0 kB > [ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)" 779 > kB [ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB > [ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB > [ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc > -examples" 6,227 kB > [ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB > [ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug > -doc -examples -test%" 14,843 kB > [ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB > [ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB > [blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) > > So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no > qca-1.0-r3 installed! :-( > What's happening? > Regards > emilio
It's quite simple really. You didn't see a '<' character. It's here: <app-crypt/qca-1.0-r3 The thing that is blocking qca-2 MUST BE a version less than 1.0-r3 There is only one sane way to resolve blockers. Run emerge with -t to find out why stuff is being pulled in. Then find out what you already have, I use eix for this. Finally solve the problem with a great big fat hefty dose of "look and think" -- alan dot mckinnon at gmail dot com
