Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 686712 - dev-ruby/metasm-1.0.4: Detected file collision(s): /usr/bin/disassemble
Summary: dev-ruby/metasm-1.0.4: Detected file collision(s): /usr/bin/disassemble
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Rick Farina (Zero_Chaos)
URL:
Whiteboard:
Keywords:
: 801331 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-05-25 00:29 UTC by Anton Bolshakov
Modified: 2021-09-18 02:30 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Bolshakov 2019-05-25 00:29:00 UTC
dev-ruby/metasm is slotted currently, however it installs one common binary:
/usr/bin/disassemble

It is not possible to install both slots or upgrade smoothly currently. The error message is:

 * Messages for package dev-ruby/metasm-1.0.4:

 * 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 https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 *      /usr/bin/disassemble
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-ruby/metasm-1.0.2-r4:1.0.2::gentoo
 *      /usr/bin/disassemble
 * 
 * Package 'dev-ruby/metasm-1.0.4' NOT merged due to file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.


Please unslot the package or fix the necessary

Thank you
Comment 1 coKe 2019-09-11 17:43:30 UTC
Same issue here.
Comment 2 Agostino Sarubbo gentoo-dev 2021-07-09 15:33:43 UTC
*** Bug 801331 has been marked as a duplicate of this bug. ***
Comment 3 Hank Leininger 2021-08-07 22:39:01 UTC
This happens still/again with metasm-1.0.4 and metasm-1.0.5; they claim separate slots and presumably should be able to coexist, but they collide on /usr/bin/disassemble

That was noted in recent bug #801331 marked as a dupe of this one.
Comment 4 Larry the Git Cow gentoo-dev 2021-09-18 02:30:56 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf8f8e4d8d86c80b86de38a1af7490c4b60e34ca

commit bf8f8e4d8d86c80b86de38a1af7490c4b60e34ca
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2021-09-18 02:21:14 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2021-09-18 02:30:38 +0000

    dev-ruby/metasm: unslot
    
    Pentoo seems to already be unmerging the older version anyway
    so isn't intending to install them in parallel.
    
    We can always re-slot it in future, but nowadays, we end up
    using =..* for Ruby deps anyway most of the time.
    
    Closes: https://bugs.gentoo.org/686712
    Signed-off-by: Sam James <sam@gentoo.org>

 ...{metasm-1.0.4.ebuild => metasm-1.0.4-r1.ebuild} | 26 +++++++++++++---------
 ...{metasm-1.0.5.ebuild => metasm-1.0.5-r1.ebuild} | 24 +++++++++++---------
 2 files changed, 29 insertions(+), 21 deletions(-)