| Summary: | dev-python/gnome-python-extras-2.19.1-r2 collisions | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mieszkoslusarczyk |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Helmut Jarausch
2008-10-20 09:52:45 UTC
Just unmerge dev-python/gnome-python-extras and proceed with updating. The -r3 version of this package should be automatically reinstalled by the update-process... I suggest dev-python/gnome-python-extras-2.19.1-r3 blocks dev-python/gnome-python-extras-2.19.1-r2, this will helps when users are updating, to remove -r2 before the updating process. (In reply to comment #1) > Just unmerge dev-python/gnome-python-extras and proceed with updating. The -r3 > version of this package should be automatically reinstalled by the > update-process... > in fact, base (which is include by split packages) does that already, so I don't see why you are all hitting this. I couldn't reproduce on my work box either while upgrading it. confirming the collision. confirming is pretty much useless here, it appears people can get to this problem while I can't. Please post an emerge --tree of whatever you do (world, gnome, ...), thanks. Fixed without a revbump... the blocker dep was just wrong. Thanks *** Bug 244427 has been marked as a duplicate of this bug. *** |