Summary: | x11-libs/cairo-0.2 (is blocking x11-libs/cairo-1.0.2) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gustav Schaffter <gustav.schaffter> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | blubb |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch to remove the nasty check |
Description
Gustav Schaffter
2006-01-07 01:16:08 UTC
Yes, you need to unmerge the old version. *** This bug has been marked as a duplicate of 79606 *** Which I did, and it all worked out fine. I guess I was surpriced that an old version was blocking a newer version of the same package. Thought that would be done through an update (??). Hope it won't happen with python or gcc or somesuch. ;-) Anyway, unmerge plus merge solved it. Biker reopening to re-assign blocking another version in the same SLOT of the same package is just plainly wrong. Normally an update would exactly solve this problem, the only reason this was done is the kinda strange check mentioned in bug 85285 comment 3. There is a patch, I think it should be applied and sent upstream instead of doing senseless blocking. Created attachment 77085 [details, diff]
patch to remove the nasty check
0.2 is no longer in portage. Closing as fixed. |