From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SfY5h-00025d-QY for garchives@archives.gentoo.org; Fri, 15 Jun 2012 15:05:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6D0BF21C049 for ; Fri, 15 Jun 2012 15:05:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id AA087E08D1 for ; Fri, 15 Jun 2012 14:30:10 +0000 (UTC) Received: from localhost (p4FF9BDB4.dip.t-dialin.net [79.249.189.180]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: tomka) by smtp.gentoo.org (Postfix) with ESMTPSA id 5CC5E1B403C for ; Fri, 15 Jun 2012 14:30:05 +0000 (UTC) Date: Fri, 15 Jun 2012 16:22:15 +0200 From: Thomas Kahle To: gentoo-science@lists.gentoo.org Subject: Re: [gentoo-science] keeping my sage keywords up-to-date Message-ID: <20120615142215.GA29976@schlaumatte.Speedport_W723_V_Typ_A_1_00_092> References: <20120615085241.GB10383@schlaumatte.Speedport_W723_V_Typ_A_1_00_092> <27344342.xWffVIXlKi@cschwan-laptop> <20120615120442.GA23115@schlaumatte.Speedport_W723_V_Typ_A_1_00_092> <2725494.95s8CXTbYi@cschwan-laptop> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@lists.gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <2725494.95s8CXTbYi@cschwan-laptop> X-Arbitrary-Number-Of-The-Day: 42 User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: f19e1d19-8188-46bf-8e32-3236f182c45f X-Archives-Hash: ad45015f2b735c0e97a80396d6ab5a16 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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, > > > >=20 > > > > I'm running sage on a mostly stable amd64 system. I wonder if some= body > > > > 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? > > > >=20 > > > > Thanks, > > > > Thomas > > >=20 > > > 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). D= id > > > you > > > see that file/do you have any problems with it? > >=20 > > 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: > >=20 > > !!! Multiple package instances within a single package slot have been p= ulled > > !!! into the dependency graph, resulting in a slot conflict: > >=20 > > dev-python/pexpect:0 > >=20 > > (dev-python/pexpect-2.4-r1::sage-on-gentoo, ebuild scheduled for merg= e) > > pulled in by (no parents that aren't satisfied by other packages in this > > slot) > >=20 > > (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 schedu= led > > for merge) (and 1 more with the same problem) > >=20 > > sci-mathematics/maxima:0 > >=20 > > (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) > >=20 > > (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) > >=20 > > dev-python/numpy:0 > >=20 > > (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) > >=20 > > (dev-python/numpy-1.6.1-r1::gentoo, ebuild scheduled for merge) pulle= d in > > by (no parents that aren't satisfied by other packages in this slot) > >=20 > > sci-mathematics/singular:0 > >=20 > > (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) > >=20 > > (sci-mathematics/singular-3.1.4-r1::gentoo, ebuild scheduled for merg= e) > > pulled in by (no parents that aren't satisfied by other packages in this > > slot) >=20 > Hm, I saw this kind of problem before and also experienced it myself with= =20 > numpy, but I never understood _why_ it happened. Did you check that these= =20 > 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.) =20 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 --=20 Thomas Kahle http://dev.gentoo.org/~tomka/ --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iJwEAQEIAAYFAk/bRRcACgkQQYXt1pFHaaH2KAP+K+RzCIiSMC2tJ0qi3FIVwfhg qRmC3N2YWYsqUHojz9Ys5fVvG6CP0Px2lPCrxGhTXkWNsXVHsIU16R8csIcFvBy/ GlNRD8d5OK1qpml03fMJCu8fwPR1zohcCZtwC8eBmzOeaHr4VEjQZCRd1AtCj/sk o50xurbPFADSQdZann8= =WTyH -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--