From: "Andrey G. Grozin" <A.G.Grozin@inp.nsk.su>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci-mathematics/reduce on amd64
Date: Fri, 23 Dec 2011 23:24:12 +0700 (NOVT) [thread overview]
Message-ID: <alpine.LRH.1.10.1112232321350.5637@star.inp.nsk.su> (raw)
In-Reply-To: <20111222163147.GB13908@poincare.pc.linmpi.mpg.de>
On Thu, 22 Dec 2011, Miguel de Val-Borro wrote:
> I have upgraded from reduce-20110414 to reduce-20110414-r1 and got a file
> collision during merging:
>
> * sci-mathematics/reduce-20110414
> * /usr/lib64/reduce/reduce.doc
> * /usr/lib64/reduce/reduce.fonts
> *
> * Package 'sci-mathematics/reduce-20110414-r1' NOT merged due to file
> * collisions. If necessary, refer to your elog messages for the whole
> * content of the above message.
Yes, I saw this behaviour. I think this must be a bug in portage. The
directories /usr/lib64/reduce/reduce.doc and
/usr/lib64/reduce/reduce.fonts belong to the old version of reduce, which
is being removed during this install. Why are they triggering file
collision??
Andrey
next prev parent reply other threads:[~2011-12-23 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 14:03 [gentoo-science] sci-mathematics/reduce on amd64 (fwd) Andrey G. Grozin
2011-12-21 15:30 ` Kacper Kowalik
2011-12-22 12:26 ` [gentoo-science] sci-mathematics/reduce on amd64 Andrey G. Grozin
2011-12-22 15:36 ` Honza Macháček
2011-12-22 16:31 ` Miguel de Val-Borro
2011-12-23 16:24 ` Andrey G. Grozin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-11 4:42 [gentoo-science] blas/lapack stuff Andrey G. Grozin
2011-10-11 7:43 ` Andrea Arteaga
2011-12-21 10:39 ` [gentoo-science] sci-mathematics/reduce on amd64 Andrey G. Grozin
2011-12-21 11:01 ` Kacper Kowalik
2011-12-21 11:13 ` Miguel de Val-Borro
2011-12-21 13:53 ` Andrey G. Grozin
2011-12-21 14:24 ` Burcin Erocal
2011-12-21 14:57 ` Andrey G. Grozin
2011-12-21 14:35 ` Christopher Schwan
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=alpine.LRH.1.10.1112232321350.5637@star.inp.nsk.su \
--to=a.g.grozin@inp.nsk.su \
--cc=gentoo-science@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