From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Cc: Vitaly Lipatov <lav@altlinux.org>
Subject: Re: [devel] libmpfr vs. libgmp: file conflicts
Date: Sun, 23 Apr 2006 01:08:27 +0400
Message-ID: <20060422210827.GB5331@basalt.office.altlinux.org> (raw)
In-Reply-To: <20060419164156.GC26909@basalt.office.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Wed, Apr 19, 2006 at 08:41:56PM +0400, Dmitry V. Levin wrote:
> On Wed, Apr 19, 2006 at 08:17:53PM +0400, Dmitry V. Levin wrote:
> > On Wed, Apr 19, 2006 at 05:59:15PM +0300, Victor Forsyuk wrote:
> > > Oops!
> > >
> > > file /usr/include/mpf2mpfr.h from install of libgmp-devel-4.1.4-alt3 conflicts with file from package libmpfr-devel-2.1.1-alt1
> > > file /usr/include/mpfr.h from install of libgmp-devel-4.1.4-alt3 conflicts with file from package libmpfr-devel-2.1.1-alt1
> > > file /usr/share/info/mpfr.info.bz2 from install of libgmp-devel-4.1.4-alt3 conflicts with file from package libmpfr-devel-2.1.1-alt1
> > > E: Error while running transaction
> >
> > Как интересно. То ни одной не было, а то сразу две. И с какой
> > рекомендуете собирать GNU Fortran?
>
> Понятно, mpfr живёт отдельной от gmp жизнью, надо собирать mpfr-2.2.0 так,
> как это делают в Debian.
> Maintainerof(mpfr), на вас можно в этом рассчитывать, или придётся делать
> всё это мне?
Виталий, отсутствие реакции можно расценивать как факт того, что судьба
mpfr вам уже не интересна?
P.S. Не то чтобы я не мог выложить какой-нибудь пакет, не поинтересовавшись
мнением мантейнера, но всё-таки есть формальная процедура, которой следует
придерживаться, во избежание нарастания бардака.
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-04-22 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:59 Victor Forsyuk
2006-04-19 16:17 ` Dmitry V. Levin
2006-04-19 16:41 ` Dmitry V. Levin
2006-04-22 21:08 ` Dmitry V. Levin [this message]
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=20060422210827.GB5331@basalt.office.altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=lav@altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git