It seems that python-updater will always re-emerge dev-libs/boost. This is especially apparent if you are doing a python-updater update that gets interrupted midway and you have to restart, boost will get re-emerged at the start even if it was already done in the previous run. Reproducible: Always
Well, can you send us the result of "equery depends boost" ? Maybe, it's another package who needs boost. Can you give us also the version of python-updater you emerge ? How do you emerge python-updater ? By an "emerge python-updater" or by using some emerge options ?
I don't mean to say that emerging python updater emerges boost. Rather that *running* python-updater does. For completeness: psicose tmp # equery depends boost [ Searching for packages depending on boost... ] sci-chemistry/openbabel-2.2.0 (dev-libs/boost) I've reproduced this problem on a number of systems (with different configurations, but all with Boost installed) here when running python-updater.
This is a known issue. It is impossible for portage to determine which version these packages have been emerged with, so if they're installed, they will always be emerged. Not optimal, but the only way to not have random breakage. From "man python-updater": manual python-updater has a list of packages that are known to break by python upgrades but can't be determined by methods specified above. This check can be disabled if you're sure you've rebuilt the package once and it's OK now. Enabled by default. use -dmanual to disable this unfortunate necessity. *** This bug has been marked as a duplicate of bug 232467 ***
