Summary: | emerge -auDvN world reporting spurious conflict | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Graham Murray <gmurray> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Graham Murray
2008-04-16 07:51:16 UTC
You have ACCEPT_KEYWORDS="x86 ~x86" so you always get the very greatest versions. Apparently two packages (or their maintainers) disagree on which version of a third package should be used. If you find that both packages ought to work equally well with $SOME_VERSION of gecko-sharp, then file a bug asking the package's maintainers to address that. You may want to reuse this bug for that purpose. In the mean time, you can use /etc/portage/package.mask to stop portage from trying to upgrade gecko-sharp, or you can stop using ~x86 packages. I disagree with the ruling that this is invalid. As soon as I saw the problem, I did use /etc/portage/package.mask to prevent the upgrade. I raised the bug because I think that portage behaved incorrectly in this situation. There was no package which requires the upgraded dependent package, but there was one which specifically requires the currently installed version. This should be sufficient for portage to not attempt to upgrade the dependent package. I would agree with your comments if two packages required conflicting versions (which I have seen in the past) but that does not apply here as the already installed version satisfies all the dependencies. |