I had one user complain about this issue: <phj> It's not the first time I encounter this problem. I did try to modify an ebuild to force the use of a newer library and my changes didn't get applied for a time. And suddenly, it worked... Case at hand: wv-0.7.1.ebuild depends on libwmf-0.2.2.ebuild. (BTW this is my old submission, before I was able to commit. I will take care of it now). Originally I kept libwmf in dev-libs, later (now as I set to sort this out) I relocated it under media-libs (more apropriate along with png and jpeg stuff). Issue appears in the following way: 1. user ran emerge --pretend wv when wv-0.7.1.ebuild contained old (dev-libs) reference but libwmf was already relocated. That did not find the dependency apparently. 2. I changed an ebuild for wv. User chacks that correct entry is in place and runs emerge --pretend wv again. However emerge complains with the same error again - it is trying to look for dev-libs/libwmf instead of media-libs/libwmf. Apparently emerge did not update the cache. rm -f /var/cache/edb/deps/* resolves the situation. Resolution: ebuild timestamps should be checked and compared with timestamps on the cached dependencies.
I am unable to replicate this problem here. We *do* check mtimes on the cache files.
Note: We *did* have this problem but it shouldn't exist anymore with 1.9.1. See if you can replicate it with 1.9.1
Indeed, that was a few days ago. Now it appears to be fixed.