From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] sage-scripts' dependencies
Date: Mon, 5 Jul 2010 21:26:46 +0200 [thread overview]
Message-ID: <201007052126.46913.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <1278349224.27947.0@pavilion64>
Hi,
On Monday 05 July 2010 19:00:15 Steven Trogdon wrote:
> Hi,
>
> I encountered the following when making a fresh install of sage (~136
> packages) within a 32bit chroot. Emerge of sage terminated because of the
> following line
>
> dosym $(which gp) "${SAGE_LOCAL}"/bin/sage_pari || die
>
> in the sage-scripts ebuild. In emerging sage, sage-scripts gets pulled in
> before pari and thus the failure. I suppose it would be awkward to have
> sage-scripts depend on pari when only a symlink is created? This can be
> replicated if one has a working sage by removing pari and sage-scripts and
> either updating world or re-emerging sage-core. Here, sage-scripts gets
> pulled in before pari and the update/emerge fails.
Thats defintely a bug - I am currently testing if the link is actually needed.
>
> Steve
Christopher
next prev parent reply other threads:[~2010-07-05 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 17:00 [gentoo-science] sage-scripts' dependencies Steven Trogdon
2010-07-05 19:26 ` Christopher Schwan [this message]
2010-07-05 23:35 ` François Bissey
2010-07-06 0:41 ` Steven Trogdon
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=201007052126.46913.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--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