- as part of a world update portage wanted to emerge boost 1.41 (dev-libs/boost-1.41.0-r3) - compilation failed with "bjam-1_41: command not found" - i found out that "dev-util/boost-build-1.41.0" was actually no installed - i check DEPEND in boost 1.41 - looks sane - i ask portage to pretend-install just dev-libs/boost-1.41.0-r3 -> pulls in dev-util/boost-build-1.41.0 - i ask portage to pretend-update world (emerge --update --keep-going @system @world) -> pulls in boost but _not_ boost-build
(In reply to comment #0) > - i ask portage to pretend-update world (emerge --update --keep-going @system > @world) -> pulls in boost but _not_ boost-build Does --deep make any difference. Please post --pretend --debug output for the command that produces incorrect results.
Created attachment 221565 [details] Case with boost-build dependency missing (In reply to comment #1) > Does --deep make any difference. Yes. > Please post --pretend --debug output for the command that produces incorrect results. Attached. Comand was: # emerge --pretend --debug --tree --update --keep-going @system @world
Since dev-texlive/texlive-psutils-2008 needed to be uninstalled, it triggered --complete-graph mode in order to check for reverse dependencies. Somehow the unbuilt dev-libs/boost-1.41.0-r3 ebuild got pulled into the graph at this point, even though no new packages are supposed to be pulled in when the --complete-graph code is doing it's thing. I'm not sure how it could have gotten pulled in here, so I need to review the code some more.
I didn't try to reproduce this but I'm pretty sure it's fixed in svn r15503.
This is fixed in 2.1.8 and 2.2_rc64.
