On 12/05/2010 08:28 AM, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm doing something wrong, or I'm making the
> sagenb spkg wrongly or this is a real issue.
I've reproduced this when upgrading "manually" from a copy ('cp -a') of
vanilla 4.6 to 4.6.1.alpha3 on OS X 10.6 (bsd.math)
http://groups.google.com/group/sage-release/browse_thread/thread/8dbb88f4bb9a6c27/fca9c2ed57255675?#fca9c2ed57255675
and on Ubuntu 8.04.4 LTS (sage.math). I'm not sure yet about what's
causing it. I'll try to investigate later today (My schedule has
recently been disrupted).
Other upgrade attempts on sage.math failed. Apparently, the first run
of sage-upgrade died on
sage: An error occurred while installing cliquer-1.2.p7
and the second on
http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3/spkg/VERSION.txt
--> VERSION.txt [.]
Failed to download
'http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3/spkg/VERSION.txt'.
Abort.
Does this relate to
http://trac.sagemath.org/sage_trac/ticket/9434
? The upgrade command I used is
yes | env MAKE="make -j20" SAGE_PARALLEL_SPKG_BUILD=yes ./sage -upgrade
http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3
2>&1 | tee -a upgrade-4.6-4.6.1.alpha3-2.log
A log is at
http://sage.math.washington.edu/home/mpatel/trac/upgrade-4.6-4.6.1.alpha3-2.log
Or have I made a silly mistake(s)?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
