Bug 449918 – collision message says what *not* to do, but not what *to* do

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Dustin J. Mitchell 2013-01-03 02:47:38 UTC]

My emerge fails with:

 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. 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.

It's *extremely*, redundantly clear that I should not file a bug, but doesn't actually say what I *should* do.

And before you drop the hammer on me for filing a bug anyway, note that this bug isn't about the collision :)

Please pare down the don't-file-a-bug text and include some positive instructions.

Reproducible: Always

[Comment 1 Zac Medico 2013-01-03 02:57:47 UTC]

The message requires emphasis because otherwise people file bugs about collisions with orphan files that nothing can be done about.

[Comment 2 Zac Medico 2013-01-03 03:09:45 UTC]

In terms of positive instructions, maybe we could refer to a section in the gentoo handbook or something. File collisions can be a complex topic, so it's hard to say anything of value while keeping it brief.

[Comment 3 Alexander Berntsen (RETIRED) 2013-08-11 20:49:41 UTC]

Created attachment 355714 [details, diff]
[PATCH] Fixes half the bug

WONTFIX "pare down the don't-file-a-bug text". It should be the way it is.

I originally disagreed that we need to "include some positive instructions", but seeing as this is a reported bug, maybe we do.

I made an article on the Wiki (after asking some users where it should be/where they would be likely to look for it): <https://wiki.gentoo.org/wiki/Portage#Blocking_conflicts>.

This article is more or less a word for word copy of <http://blogs.gentoo.org/zmedico/2008/05/09/> (with Zac's permission), as I think he put it very neatly and as precisely as possible. Feel free to improve it -- it's a wiki.

The attached patch adds a link to this to emerge output.

[Comment 4 Alexander Berntsen (RETIRED) 2013-08-11 22:20:34 UTC]

Created attachment 355720 [details, diff]
[PATCH] Fixes half the bug, v2

Link to knowledge Base instead.

[Comment 5 Zac Medico 2013-08-12 03:26:00 UTC]

(In reply to Alexander Berntsen from comment #4)
> Created attachment 355720 [details, diff] [details, diff]
> [PATCH] Fixes half the bug, v2
> 
> Link to knowledge Base instead.

Thanks, this is in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ef14017dfaeeaa0b1dacdc4641c30583128f7f08

(In reply to Alexander Berntsen from comment #3)
> I made an article on the Wiki (after asking some users where it should
> be/where they would be likely to look for it):
> <https://wiki.gentoo.org/wiki/Portage#Blocking_conflicts>.

I've undone this wiki change since it would be better to put it on a separate page, or to extend the Knowledge_Base:Blockers article.

[Comment 6 Zac Medico 2013-08-13 00:04:31 UTC]

This is fixed in 2.2.0.