Summary: | gnome-applets-2.20.0 merge failed (file collision) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mik B. Shvets <solshark> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 207667 | ||
Bug Blocks: |
Description
Mik B. Shvets
2007-10-27 21:49:37 UTC
(In reply to comment #0) > * A bug report is only useful if it identifies at > * least two or more packages that are known to install the same file(s). > * If a collision occurs and you can not explain where the file came from > * then you should simply ignore the collision since there is not enough > * information to determine if a real problem exists. Please do NOT file > * a bug report at http://bugs.gentoo.org unless you report exactly which > * two packages install the same file(s). Once again, please do NOT file > * a bug report unless you have completely understood the above message. Please, re-read the above snippet a couple of times. I just came here to see if there's a recommended procedure for this, as this just happened on my gnome update on stable x86 as well. I did read the snippet so I'm not opening a bug, just adding to a closed one... From the file timestamps it seems to me that this was caused by gnome-menus-2.20.1 postinst routine running python_mod_optimize on *.py -files from the pre-existing <gnome-base/gnome-applets-2.20.0 package, so the generated *.pyc and *.pyo -files really don't belong to any package. Removing those files manually of course fixes this, but is there any way to avoid this in the first place? Not my knowledge. It was probably due to a wrong ebuild or eclass at some point. The proper fix is to remove those files and remerge the package like you did. Actually it seems this bug depends on bug #207667 as gnome-applets ebuild doesn't use the eclass perfectly yet. Although for all users that are already using 2.20, it won't make a difference, it will fix things for users waiting far too long to update their boxes :) |