Gentoo Archives: gentoo-science

From: Christopher Schwan <cschwan@××××××××××××××××××.de>
To: gentoo-science@l.g.o
Subject: Re: [gentoo-science] keeping my sage keywords up-to-date
Date: Fri, 15 Jun 2012 15:05:27
Message-Id: 2725494.95s8CXTbYi@cschwan-laptop
In Reply to: Re: [gentoo-science] keeping my sage keywords up-to-date by Thomas Kahle
1 On Friday 15 June 2012 14:04:42 Thomas Kahle wrote:
2 > On 12:14 Fri 15 Jun 2012, Christopher Schwan wrote:
3 > > On Friday 15 June 2012 10:52:41 Thomas Kahle wrote:
4 > > > Hi,
5 > > >
6 > > > I'm running sage on a mostly stable amd64 system. I wonder if somebody
7 > > > else does this and how they keep their keywords up-to-date. The
8 > > > autounmask feature of portage is a bit of help on first install, but
9 > > > quite useless to keep the sage tree in sync. Surely one could make a
10 > > > script that updates the keyword file based on the latest versions in
11 > > > s-o-g. Has anyone done this or implemented some other solution?
12 > > >
13 > > > Thanks,
14 > > > Thomas
15 > >
16 > > I am also using mostly stable amd64. For the keywords we have the file
17 > > package.keywords/sage which works quite well (see also the README). Did
18 > > you
19 > > see that file/do you have any problems with it?
20 >
21 > Oh yes. Sorry for not reading the manual. Now I have an up-to-date
22 > package.keywords and I'm back to the case where portage can't make up
23 > its mind which version of a package to install:
24 >
25 > !!! Multiple package instances within a single package slot have been pulled
26 > !!! into the dependency graph, resulting in a slot conflict:
27 >
28 > dev-python/pexpect:0
29 >
30 > (dev-python/pexpect-2.4-r1::sage-on-gentoo, ebuild scheduled for merge)
31 > pulled in by (no parents that aren't satisfied by other packages in this
32 > slot)
33 >
34 > (dev-python/pexpect-2.0-r1::sage-on-gentoo, installed) pulled in by
35 > ~dev-python/pexpect-2.0 required by
36 > (sci-mathematics/sage-notebook-0.8.29-r1::sage-on-gentoo, ebuild scheduled
37 > for merge) (and 1 more with the same problem)
38 >
39 > sci-mathematics/maxima:0
40 >
41 > (sci-mathematics/maxima-5.27.0-r1::gentoo, ebuild scheduled for merge)
42 > pulled in by (no parents that aren't satisfied by other packages in this
43 > slot)
44 >
45 > (sci-mathematics/maxima-5.26.0::gentoo, installed) pulled in by
46 > ~sci-mathematics/maxima-5.26.0[ecls] required by
47 > (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
48 >
49 > dev-python/numpy:0
50 >
51 > (dev-python/numpy-1.5.1::sage-on-gentoo, installed) pulled in by
52 > ~dev-python/numpy-1.5.1 required by
53 > (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
54 >
55 > (dev-python/numpy-1.6.1-r1::gentoo, ebuild scheduled for merge) pulled in
56 > by (no parents that aren't satisfied by other packages in this slot)
57 >
58 > sci-mathematics/singular:0
59 >
60 > (sci-mathematics/singular-3.1.3.3::gentoo, installed) pulled in by
61 > ~sci-mathematics/singular-3.1.3.3 required by
62 > (sci-mathematics/sage-5.0-r1::sage-on-gentoo, installed)
63 >
64 > (sci-mathematics/singular-3.1.4-r1::gentoo, ebuild scheduled for merge)
65 > pulled in by (no parents that aren't satisfied by other packages in this
66 > slot)
67
68 Hm, I saw this kind of problem before and also experienced it myself with
69 numpy, but I never understood _why_ it happened. Did you check that these
70 package are not in world?

Replies

Subject Author
Re: [gentoo-science] keeping my sage keywords up-to-date Thomas Kahle <tomka@g.o>