portage can't build package when there is other one installed, which blocks package we want to build. let me give an example: <root@CogES>/tmp: emerge -p vnc These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] net-misc/tightvnc (from pkg net-misc/vnc-3.3.7-r1) [ebuild N ] net-misc/vnc-3.3.7-r1 as we see here all dependencies are already installed, the only problem is that there is tightvnc, which blocks vnc. let see what'll happen when i want to build package for vnc: <root@CogES>/tmp: emerge -B vnc Calculating dependencies ...done! !!! --buildpkgonly requires all dependencies to be merged. !!! Cannot merge requested packages. Merge deps and try again. portage thinks that tightvnc is a dependency of vnc and won't build package Reproducible: Always Steps to Reproduce: 1. have some blockers in system 2. have all needed dependencies installed 3. want to build package Actual Results: portage says that not all dependencies are installed Expected Results: portage should build package
Created attachment 30521 [details] patch for portage.py It's a patch, which solves described problem
Do not modify data when doing checks. Fixed in cvs. >=portage-2.0.51_pre9
it seems to be broken till now (i'm using portage-2.0.51_rc1): <root@CogES>~: emerge -p xfree These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] x11-base/xorg-x11 (from pkg x11-base/xfree-4.3.0-r7) [ebuild N ] x11-base/xfree-4.3.0-r7 <root@CogES>~: emerge -B xfree Calculating dependencies ...done! !!! --buildpkgonly requires all dependencies to be merged. !!! Cannot merge requested packages. Merge deps and try again.
*** Bug 61230 has been marked as a duplicate of this bug. ***
nick->"Fixed in cvs. >=portage-2.0.51_pre9" Marcin 'aye' Kryczek->"it seems to be broken till now (i'm using portage-2.0.51_rc1)" Interpretting his comments above as "it's still horked". Unable to check it atm, but anyone know offhand if it's still broke?
*** Bug 92828 has been marked as a duplicate of this bug. ***
*** Bug 96457 has been marked as a duplicate of this bug. ***
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
