From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] file collisions
Date: Thu, 26 May 2011 21:08:35 +0100 [thread overview]
Message-ID: <201105262108.36400.michaelkintzios@gmail.com> (raw)
In-Reply-To: <yu9d3j5e9ah.fsf@nyu.edu>
[-- Attachment #1: Type: Text/Plain, Size: 1333 bytes --]
On Thursday 26 May 2011 17:06:14 Allan Gottlieb wrote:
> On Thu, May 26 2011, Alex Schuster wrote:
> > Allan Gottlieb writes:
> >> 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?
> >
> > Yes. If you think these files might be important, then you could back
> > them up first. Apparently they belong to the icu stuff you are going to
> > remerge anyway, so deleting should be safe I think. But it's strange
> > that those files do not belong to any package.
> >
> > Instead of removing them it would be easier to set FEATURES to
> > -collision- protect. And with FEATURES=keepwork you will not have to
> > recompile icu. So, I would do this:
> >
> > FEATURES="-collision-protect keepwork" emerge -1a dev-libs/icu
> >
> > Remember that you have to delete stuff in /var/tmp/portage/dev-
> > libs/icu-4.6.1 manually afterwards.
>
> thank you for the advice, which worked fine.
I could swear I saw the same/similar message about collisions, but in my case
the package emerged and the files were overwritten. Not sure if I have some
FEATURES setting that took care of this.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-26 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 12:15 [gentoo-user] file collisions Allan Gottlieb
2011-05-26 12:28 ` Alex Schuster
2011-05-26 16:06 ` Allan Gottlieb
2011-05-26 20:08 ` Mick [this message]
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=201105262108.36400.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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