Summary: | emerge -puDNt world - cairo downgrades then upgrades | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | barrie backhurst <barrie.backhurst> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | brebs, hurikhan77+bgo |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
barrie backhurst
2006-08-16 04:17:43 UTC
May I ask why are you mixing latest unstable cairo w/ stable ebuilds? Upgrade dev-python/pycairo to latest unstable and you won't have the cycle. (In reply to comment #1) > May I ask why are you mixing latest unstable cairo w/ stable ebuilds? Upgrade > dev-python/pycairo to latest unstable and you won't have the cycle. > It was a dependancy a while back, for an ebuild I cannot remember. I have now removed it from package.keywords and am currently updating world. I just had not experienced this previously and felt I should report it, in case it was significant. Why has this been marked invalid? What valid reason is there for Portage to upgrade a package *more* than once in a single run, when the package isn't slotted? (In reply to comment #3) > Why has this been marked invalid? See Bug 48195. Closing. *** Bug 153116 has been marked as a duplicate of this bug. *** |