From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] file collisions
Date: Thu, 26 May 2011 08:15:16 -0400 [thread overview]
Message-ID: <yu9y61tejzf.fsf@nyu.edu> (raw)
emerge complains that icu (details below) will overwrite files that MAY
belong to other packages. But in fact none do. The suggestion is to
ignore the collisions. Does that mean I should simply rm the files
before retrying the emerge?
thanks,
allan
* Messages for package dev-libs/icu-4.6.1:
* Package: dev-libs/icu-4.6.1
* Repository: gentoo
* Maintainer: arfrever@gentoo.org
* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
* FEATURES: sandbox
* Applying icu-4.6.1-parallel_installation.patch ...
* 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.
*
* package dev-libs/icu-4.6.1 NOT merged
*
* Detected file collision(s):
*
* /usr/lib64/libicutu.so.46.1
* /usr/lib64/libicuio.so.46.1
* /usr/lib64/libiculx.so.46.1
* /usr/lib64/libicutest.so.46.1
* /usr/lib64/libicudata.so.46.1
* /usr/lib64/libicui18n.so.46.1
* /usr/lib64/libicuuc.so.46.1
* /usr/lib64/libicule.so.46.1
* /usr/lib64/icu/4.6.1/Makefile.inc
* /usr/lib64/icu/4.6.1/pkgdata.inc
* /usr/share/doc/icu-4.6.1/unicode-license.txt.bz2
* /usr/share/doc/icu-4.6.1/html/readme.html
* /usr/share/icu/4.6.1/install-sh
* /usr/share/icu/4.6.1/license.html
* /usr/share/icu/4.6.1/mkinstalldirs
* /usr/share/icu/4.6.1/config/mh-linux
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'dev-libs/icu-4.6.1' NOT merged due to file collisions. If
* necessary, refer to your elog messages for the whole content of the
* above message.
*
next reply other threads:[~2011-05-26 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 12:15 Allan Gottlieb [this message]
2011-05-26 12:28 ` [gentoo-user] file collisions Alex Schuster
2011-05-26 16:06 ` Allan Gottlieb
2011-05-26 20:08 ` Mick
2011-05-26 20:38 ` Alex Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yu9y61tejzf.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox