Thanks, Michael. Obviously do not spend any (more) time on this before 3.3 is out. Or maybe 3.4. or 3.4.1. or...
see http://www.warwick.ac.uk/staff/J.E.Cremona/upgrade.tgz for the install log and env output. I could not do either "hg heads" or "hg status" in sage-3.3.rc0/devel/ sage : j...@ubuntu%pwd /home/john/sage-3.3.rc0/devel/sage j...@ubuntu%hg heads abort: requirement 'fncache' not supported! j...@ubuntu%hg status abort: requirement 'fncache' not supported! Googling suggests that there is a mismatch between the versions of hg in use. Mine is 0.9.5 while Sage has 1.0.1 which looks as if it might be a cause of some problems. There is no more recent version in the ubuntu repository I use. Anyway, using "sage -hg" instead of hg gives the same errors. (Normally I only ever use hg from the Sage command- line using hg_sage.apply() and the like.) John On Feb 21, 5:04 pm, mabshoff <[email protected]> wrote: > On Feb 21, 8:57 am, John Cremona <[email protected]> wrote: > > > On Feb 21, 3:45 pm, John Cremona <[email protected]> wrote: > > Hi John, > > > > > > I'm now doing an upgrade from my rc0 build, not from any clone, and > > > we'll see what happens! > > > The upgrade failed in exactly the same way as above. To recap: I had > > a working successful build of sage-3.3.rc0 and was in the main branch > > (so starting sage did not give me a message about bing in a different > > mercurial branch). I typed "sage -upgrade" followed by "y" at the > > prpmpt, and went to work on something else. When I came back it had > > finished, so I typed "sage" and got the error already reported: the > > banner still says rc0 and there's an error on startup, saying > > > ImportError: libpynac-0.1.so.2: cannot open shared object file: No > > such file or directory > > Error importing ipy_profile_sage - perhaps you should run %upgrade? > > WARNING: Loading of ipy_profile_sage failed. > > > I particularly like the suggestion that my problem is to upgrade > > (which does nothing, of course). > > Ok, please send us a link to the compressed install.log from the build > as well as the upgrade (it should be all in one file) and I will take > a look. > > Right now I would suspect that either the spkgs you download are > corrupted or that another sage install is interfering via some bits of > the Sage environment, so please also send the output from 'env' on > that box and even better from the shell of the failed upgrade if you > still have it. > > Can you make 100% sure that "hg heads" in the current Sage library > branch that you use shows only one head and that hg status does not > show any oddities? > > > I am going to need a lot of persuading before trying an upgrade again, > > which is a pity since I'll only have time to download and build sage > > while at home for a while, and my internet connection is not so fast > > in rural Warwickshire (especially when my daughter is watching TV on > > her laptop!) so downloading the whole distribution takes a couple of > > hours. > > Yeah, the main US site has gotten quite slow, even though that might > not be the cause for your slow rural connection :) > > > John > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
