Gentoo Archives: gentoo-science

From: Thomas Kahle <tomka@g.o>
To: gentoo-science@l.g.o
Subject: Re: [gentoo-science] keeping my sage keywords up-to-date
Date: Fri, 15 Jun 2012 15:05:38
Message-Id: 20120615142215.GA29976@schlaumatte.Speedport_W723_V_Typ_A_1_00_092
In Reply to: Re: [gentoo-science] keeping my sage keywords up-to-date by Christopher Schwan
On 14:29 Fri 15 Jun 2012, Christopher Schwan wrote:
> On Friday 15 June 2012 14:04:42 Thomas Kahle wrote: > > 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) > > Hm, I saw this kind of problem before and also experienced it myself with > numpy, but I never understood _why_ it happened. Did you check that these > package are not in world?
Well, sci-mathematics/singular is in world, but singular-3.1.3 satisfies this dependency so it should be no problem. To me this looks like a portage quirk. Also note that I don't get these messages without the -D option of portage (but it also does not pick up possible upgrades in this case.) OK, I just tried removing singular and maxima from the world file and then it works. It still shows the two messages for numpy and pexpect, they are just not fatal anymore. I don't see through... Cheers, Thomas -- Thomas Kahle http://dev.gentoo.org/~tomka/

Attachments

File name MIME type
signature.asc application/pgp-signature