Summary: | circular dependency when trying to upgrade openssl or "world" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vieri <rentorbuy> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Vieri
2014-07-29 08:07:40 UTC
I'm not sure what you expect here, this is normal Portage behavior for some USE flags to trigger circular dependencies It even printed you suggestions for solving the circular: It might be possible to break this cycle by applying any of the following changes: - dev-libs/openssl-1.0.1h-r2 (Change USE: -kerberos) - app-crypt/mit-krb5-1.12.1-r1 (Change USE: -pkinit) Note that this change can be reverted, once the package has been installed. (In reply to Samuli Suominen from comment #1) > It even printed you suggestions for solving the circular: > > It might be possible to break this cycle > by applying any of the following changes: > - dev-libs/openssl-1.0.1h-r2 (Change USE: -kerberos) > - app-crypt/mit-krb5-1.12.1-r1 (Change USE: -pkinit) > > Note that this change can be reverted, once the package has been installed. I read the suggestion but I didn't understand why I should, eg., remove "kerberos" from openssl so I can emerge both openssl and mit-krb5 and then once I have them both, re-emerge openssl with "kerberos". Is that really the way to do this? Yes, that's how you resolve circular deps like these. That's why it was suggested in the emerge output. (In reply to Ben Kohler from comment #3) > Yes, that's how you resolve circular deps like these. That's why it was > suggested in the emerge output. or maybe one of the 2 ebuilds could be modified by setting PDEPEND. BTW, this circular dependency is new. I installed a fresh system a couple of weeks ago (with the same packages and same automated emerge commands within a custom script) and did not see this issue. So the openssl / mit-krb5 circular dependency condition is very recent. This is a bug tracker and not a support forum. Try our web forums, mailing lists or IRC channels instead. (In reply to Jeroen Roovers from comment #5) > This is a bug tracker and not a support forum. Try our web forums, mailing > lists or IRC channels instead. I consider it a bug if a circular dependency appears when it didn't before and it breaks my "emerge world" but OK, I'll just post to the forum. Improving ebuilds is also a bug fix or enhancement. Fortunately this isn't a major issue. |