* [gentoo-science] keeping my sage keywords up-to-date @ 2012-06-15 8:52 Thomas Kahle 2012-06-15 9:17 ` Francois Bissey 2012-06-15 10:14 ` Christopher Schwan 0 siblings, 2 replies; 6+ messages in thread From: Thomas Kahle @ 2012-06-15 8:52 UTC (permalink / raw To: Gentoo Science [-- Attachment #1: Type: text/plain, Size: 496 bytes --] 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 -- Thomas Kahle http://dev.gentoo.org/~tomka/ [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 316 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-science] keeping my sage keywords up-to-date 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 1 sibling, 0 replies; 6+ messages in thread From: Francois Bissey @ 2012-06-15 9:17 UTC (permalink / raw To: gentoo-science On Fri, 15 Jun 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? > Hi Thomas, we provide a package.keyword file that you can link too and we try to maintain it properly. There is the occasional break when we do a clean but you can use it. It is part of the overlay so if you didn't change layman settings it should be /var/lib/layman/sage-on-gentoo/package.keywords/sage There is also a package.use file. Francois ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-science] keeping my sage keywords up-to-date 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 1 sibling, 1 reply; 6+ messages in thread From: Christopher Schwan @ 2012-06-15 10:14 UTC (permalink / raw To: gentoo-science 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? Cheers, Christopher ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-science] keeping my sage keywords up-to-date 2012-06-15 10:14 ` Christopher Schwan @ 2012-06-15 12:04 ` Thomas Kahle 2012-06-15 12:29 ` Christopher Schwan 0 siblings, 1 reply; 6+ messages in thread From: Thomas Kahle @ 2012-06-15 12:04 UTC (permalink / raw To: gentoo-science [-- 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 --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-science] keeping my sage keywords up-to-date 2012-06-15 12:04 ` Thomas Kahle @ 2012-06-15 12:29 ` Christopher Schwan 2012-06-15 14:22 ` Thomas Kahle 0 siblings, 1 reply; 6+ messages in thread From: Christopher Schwan @ 2012-06-15 12:29 UTC (permalink / raw To: gentoo-science 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? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-science] keeping my sage keywords up-to-date 2012-06-15 12:29 ` Christopher Schwan @ 2012-06-15 14:22 ` Thomas Kahle 0 siblings, 0 replies; 6+ messages in thread From: Thomas Kahle @ 2012-06-15 14:22 UTC (permalink / raw To: gentoo-science [-- Attachment #1: Type: text/plain, Size: 3771 bytes --] 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/ [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 316 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-06-21 21:04 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2012-06-15 12:29 ` Christopher Schwan 2012-06-15 14:22 ` Thomas Kahle
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox