On Sat, Feb 21, 2009 at 2:56 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, > > <SNIP> > >> 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 > > William run into similar issues and tracked this down to a stale left > over pynac library. The fix is to delete them in spkg-install. This is > now a 3.4 blocker at > > #5333 (pynac.spkg: Delete old pynac libray during spkg-install >
I just want to point out that I didn't actually hit that problem and that wasn't the fix for the problem I saw, though it is a very good idea :-). My problem was a problem merging two heads in the main sage branch, since I had made a lot of changes to it. The fix was to delete sage-main and install it again from scratch. William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
