Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 649742 - www-apps/chromedriver-bin with www-client/chromium-64.0.3282.186:0::gallifrey - file collision in /usr/bin/chromedriver
Summary: www-apps/chromedriver-bin with www-client/chromium-64.0.3282.186:0::gallifrey...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Austin English (RETIRED)
Depends on:
Reported: 2018-03-06 13:52 UTC by Marco Genasci
Modified: 2018-06-27 00:14 UTC (History)
1 user (show)

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

chromedriver-bin-2.35-r1.ebuild.patch (0001-www-apps-chromedriver-bin-fix-file-collision-chromiu.patch,1.28 KB, patch)
2018-03-06 13:55 UTC, Marco Genasci
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Genasci 2018-03-06 13:52:24 UTC
www-apps/chromedriver-bin fails with file collision when chromium is installed because chomium already provides chromedriver:

 * 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 unless you report exactly
 * which two packages install the same file(s). See
 * 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/chromedriver
 * Searching all installed packages for file collisions...
 * Press Ctrl-C to Stop
 * www-client/chromium-64.0.3282.186:0::gallifrey
 *      /usr/bin/chromedriver
 * Package 'www-apps/chromedriver-bin-2.35' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

$ ls -l /usr/bin/chromedriver 
lrwxrwxrwx 1 root root 40 Feb  1 11:06 /usr/bin/chromedriver -> /usr/lib64/chromium-browser/chromedriver

Reproducible: Always
Comment 1 Marco Genasci 2018-03-06 13:55:27 UTC
Created attachment 522510 [details, diff]

www-apps/chromedriver-bin-2.35-r1 patch with chromium block
Comment 2 Marco Genasci 2018-03-06 14:51:03 UTC
Just a note gallifrey is my overlay but same problem there's with official chromium ebuild:

src_install() {
        doexe out/Release/chromedriver
        dosym "${CHROMIUM_HOME}/chromedriver" /usr/bin/chromedriver
Comment 3 Larry the Git Cow gentoo-dev 2018-06-27 00:12:41 UTC
The bug has been closed via the following commit(s):

commit 157dc868a0b7a933626382701a0dba6e74000bde
Author:     Marco Genasci <>
AuthorDate: 2018-06-27 00:08:40 +0000
Commit:     Zac Medico <>
CommitDate: 2018-06-27 00:11:46 +0000

    www-apps/chromedriver-bin: block www-client/chromium (bug 649742)
    Both packages install /usr/bin/chromedriver.
    Package-Manager: Portage-2.3.40, Repoman-2.3.9

 ...{chromedriver-bin-2.24.ebuild => chromedriver-bin-2.24-r1.ebuild} | 5 +++--
 ...{chromedriver-bin-2.30.ebuild => chromedriver-bin-2.30-r1.ebuild} | 5 +++--
 ...{chromedriver-bin-2.35.ebuild => chromedriver-bin-2.35-r1.ebuild} | 3 ++-
 3 files changed, 8 insertions(+), 5 deletions(-)
Comment 4 Zac Medico gentoo-dev 2018-06-27 00:14:53 UTC
Thanks for the report, I've also added the !www-client/chromium blocker in the 2.40 version bump: