| Summary: | USE_PYTHON removal of 3.2 causes depclean to fail without manual rebuilds | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Aaron Pelton <aaron.pelton> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | minor | CC: | dev-portage, mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Aaron Pelton
2014-09-08 12:36:37 UTC
Yes I did a deep/new/update use rebuild. but did not do --with-bdeps=y I'm not sure this can be fixed. @dev-portage, can you think of any way the user could end up with inconsistent dep tree like this? Can bdeps be relevant? Or dynamic-deps? (In reply to Michał Górny from comment #3) > @dev-portage, can you think of any way the user could end up with > inconsistent dep tree like this? Can bdeps be relevant? Or dynamic-deps? I think bdeps is a likely culprit. If you don't use --with-bdeps=y, then parts of your dependency graph may break like this. This is why the depclean message advises you to run the following command: emerge --update --newuse --deep --with-bdeps=y @world It's possible for dynamic-deps to lead to similar complaints from depclean, but this looks more like a bdeps issue to me. USE_PYTHON is gone. |