From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerging gentoo-sources failing due to file collisions
Date: Wed, 06 Jan 2010 20:08:19 +0100 (CET) [thread overview]
Message-ID: <tkrat.a457ba1b11bc0bc3@igpm.rwth-aachen.de> (raw)
In-Reply-To: <534c2d371001061043r31680812n2ab4afc7630eb6c0@mail.gmail.com>
On 6 Jan, Walt Rarus wrote:
> I've never experienced this phenomenon prior to gentoo-sources-2.6.31.-r6.
> I've always emerged gentoo-sources and they peacefully sat there and waited
> until I built the corresponding kernel later when I felt like it - if ever.
> With 2.6.31-r6, however, the emerge fails and consequently screws up 'emerge
> world' attempts. PITA.
>
> Any recommended workarounds or fixes?
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> I've pieced the following together from the console and elogv:
>
> ERROR: preinst
> 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 sys-kernel/gentoo-sources-2.6.31-r6 NOT merged
>
> Detected file collision(s):
>
> * /usr/src/linux-2.6.31-gentoo-r6/Makefile
> * /usr/src/linux-2.6.31-gentoo-r6/Kbuild
> .... gazillion similar ellided
*** SNIP ***
So, please check where these files came from by
qfile /usr/src/linux-2.6.31-gentoo-r6/Makefile
Have you installed this kernel 'by hand' i.e. outside of portage?
Check by uname -a if you are not currently running linux-2.6.31-r6
If not, it's safe to rm -rf /usr/src/linux-2.6.31-gentoo-r6
and emerge it again.
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
next prev parent reply other threads:[~2010-01-06 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 18:43 [gentoo-user] emerging gentoo-sources failing due to file collisions Walt Rarus
2010-01-06 19:08 ` Helmut Jarausch [this message]
2010-01-06 19:32 ` Walt Rarus
2010-01-06 19:50 ` [gentoo-user] [SOLVED] " Walt Rarus
2010-01-06 19:56 ` [gentoo-user] " Alan McKinnon
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=tkrat.a457ba1b11bc0bc3@igpm.rwth-aachen.de \
--to=jarausch@igpm.rwth-aachen.de \
--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