From: Thomas Kahle <tomka@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] keeping my sage keywords up-to-date
Date: Fri, 15 Jun 2012 14:04:42 +0200 [thread overview]
Message-ID: <20120615120442.GA23115@schlaumatte.Speedport_W723_V_Typ_A_1_00_092> (raw)
In-Reply-To: <27344342.xWffVIXlKi@cschwan-laptop>
[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]
On 12:14 Fri 15 Jun 2012, Christopher Schwan wrote:
> On Friday 15 June 2012 10:52:41 Thomas Kahle wrote:
> > Hi,
> >
> > I'm running sage on a mostly stable amd64 system. I wonder if somebody
> > else does this and how they keep their keywords up-to-date. The
> > autounmask feature of portage is a bit of help on first install, but
> > quite useless to keep the sage tree in sync. Surely one could make a
> > script that updates the keyword file based on the latest versions in
> > s-o-g. Has anyone done this or implemented some other solution?
> >
> > Thanks,
> > Thomas
>
> I am also using mostly stable amd64. For the keywords we have the file
> package.keywords/sage which works quite well (see also the README). Did you
> see that file/do you have any problems with it?
Oh yes. Sorry for not reading the manual. Now I have an up-to-date
package.keywords and I'm back to the case where portage can't make up
its mind which version of a package to install:
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-python/pexpect:0
(dev-python/pexpect-2.4-r1::sage-on-gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-python/pexpect-2.0-r1::sage-on-gentoo, installed) pulled in by
~dev-python/pexpect-2.0 required by (sci-mathematics/sage-notebook-0.8.29-r1::sage-on-gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)
sci-mathematics/maxima:0
(sci-mathematics/maxima-5.27.0-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(sci-mathematics/maxima-5.26.0::gentoo, installed) pulled in by
~sci-mathematics/maxima-5.26.0[ecls] required by (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
dev-python/numpy:0
(dev-python/numpy-1.5.1::sage-on-gentoo, installed) pulled in by
~dev-python/numpy-1.5.1 required by (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
(dev-python/numpy-1.6.1-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
sci-mathematics/singular:0
(sci-mathematics/singular-3.1.3.3::gentoo, installed) pulled in by
~sci-mathematics/singular-3.1.3.3 required by (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
(sci-mathematics/singular-3.1.4-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
--
Thomas Kahle
http://dev.gentoo.org/~tomka/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-06-15 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 8:52 [gentoo-science] keeping my sage keywords up-to-date Thomas Kahle
2012-06-15 9:17 ` Francois Bissey
2012-06-15 10:14 ` Christopher Schwan
2012-06-15 12:04 ` Thomas Kahle [this message]
2012-06-15 12:29 ` Christopher Schwan
2012-06-15 14:22 ` Thomas Kahle
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=20120615120442.GA23115@schlaumatte.Speedport_W723_V_Typ_A_1_00_092 \
--to=tomka@gentoo.org \
--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