On 23 Mrz., 22:04, Starx <jst...@gmail.com> wrote: > So I'm trying to upgrade my beta7 to beta9. It didn't work and I'm > not sure how to interpret what happened: > > ~/sage-dev/devel/sage-main Starx$ ../../sage > -upgradehttp://boxen.math.washington.edu/home/release/sage-5.0.beta9/sage-5.0... > [1] 1793 > ~/sage-dev/devel/sage-main Starx$ Downloading packages from > 'http://boxen.math.washington.edu/home/release/sage-5.0.beta9/sage-5.0.... > Reading package lists... Done! > The following packages will be upgraded: > > cvxopt-1.1.3.p1 extcode-5.0.beta9 lcalc-1.23.p10 linbox-1.1.6.p7 > maxima-5.26.0.p0 ratpoints-2.1.3.p3 sage-5.0.beta9 > sage_root-5.0.beta9 sage_scripts-5.0.beta9 singular-3-1-3-3.p6 > > ** WARNING: This is a source-based upgrade, which could take hours, > ** fail, and render your Sage install useless!! > > Do you want to continue [y/N]? y > -bash: y: command not found > > [1]+ Stopped ../../sage > -upgradehttp://boxen.math.washington.edu/home/release/sage-5.0.beta9/sage-5.0... > ~/sage-dev/devel/sage-main Starx$ > > and now I'm back at the prompt. I can run sage and beta7 starts and > functions properly. Is this not how to upgrade sage?
Upgrading *from* devel releases to later releases (stable or devel, doesn't matter) is currently "consciously" broken. Cf. some recent thread here on basing releases on the previous *devel* release. (I'm personally not very happy with the current situation, as you might already have noticed. ;-) ) -leif -- 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