[ebuild U ] dev-libs/boost-1.34.1-r2 [1.33.1-r1] USE="doc -debug -icu -pyste -tools% (-bcp%) (-bjam%) (-threads%*) (-threadsonly%)" 12,689 kB [ebuild N ] dev-util/boost-build-1.34.1 USE="python" 0 kB [blocks B ] <dev-libs/boost-1.34.0 (is blocking dev-util/boost-build-1.34.1) This is a bug. You could just replace it like this: [ebuild U ] A-3 [1] [ebuild N ] B USE="python" 0 kB [blocks B ] <A-2 (is blocking B) Of course, dev-libs/boost-1.34.0 is no longer in the portage tree - as usual. Just as it's being fun for gentoo developers to hurt gentoo users. BTW: I figured, that there is already a report for this actual problem, but as that request was closed without having fixed, I decided to inform you about the fact, that I as a Gentoo user am really pissed of that. "Closing this bug as there's no bug here. The versions have to match, end of story." The problem is a really different one. Think about it. If you don't get it, think harder. Ah, just fixed another problem: [blocks B ] app-crypt/gnupg (is blocking app-crypt/gnupg-1.9.21) Funny, eh? A packages just blocking itself. And the story continues: [blocks B ] <=app-crypt/gnupg-2.0.1 (is blocking app-crypt/gnupg-2.0.9) Ah right, I didn't mentioned it yet: app-crypt/gnupg-2.0.1 just isn't in the tree at all, too, any longer. And again and again, just ignoring all those blocks just doesn't hurt at all. Maybe some time, you manage to tell us poor users, why these pointless blocks are there in the first place. Because I just don't get the point in having an OLD version of a packages blocking another package, which will be installed AFTER the OLD packages will have been updated to a non-blocking version. Regards, Bodo Reproducible: Always
(In reply to comment #0) > [ebuild U ] dev-libs/boost-1.34.1-r2 [1.33.1-r1] USE="doc -debug -icu > -pyste -tools% (-bcp%) (-bjam%) (-threads%*) (-threadsonly%)" 12,689 kB > [ebuild N ] dev-util/boost-build-1.34.1 USE="python" 0 kB > [blocks B ] <dev-libs/boost-1.34.0 (is blocking > dev-util/boost-build-1.34.1) > > Of course, dev-libs/boost-1.34.0 is no longer in the portage tree - as usual. > Just as it's being fun for gentoo developers to hurt gentoo users. Then remove <dev-libs/boost-1.34.0 and try again. Note the "<" this probably means 1.33.1-r1 for you. The versions of boost and boost-build have to match, end of the story! :-) > Ah, just fixed another problem: > > [blocks B ] app-crypt/gnupg (is blocking app-crypt/gnupg-1.9.21) > > Funny, eh? A packages just blocking itself. And the story continues: > > [blocks B ] <=app-crypt/gnupg-2.0.1 (is blocking app-crypt/gnupg-2.0.9) > > Ah right, I didn't mentioned it yet: app-crypt/gnupg-2.0.1 just isn't in the > tree at all, too, any longer. Same as above applies here. Remove gnupg and try world update again and the new version will be pulled in! As far as I know newer versions of portage (2.2) will automatically resolve this kind of blockers.
Don't assume we like to "hurt users" or introduce "pointless blocks". They are there for a reason. In cases like the ones you mention, it is usually necessary to first unmerge the older version and then update to the newer. If you don't understand the reason, then I suggest you politely ask the concerned maintainer to enlighten you.
