`sage -upgrade` downgrades from 4.6 to 4.6.rc0
I tried to run sage -upgrade from a built-from-source installation of 4.6. Nothing seemed to happen, but now when I run sage, I get a warning telling me I'm running an unstable prerelease version, and the header says "Sage Version 4.6.rc0"! I checked $SAGE_ROOT/devel/sage/sage/version.py, and in that file the version is duly listed as 4.6. Any idea what's going on?
-EDIT-
The files at $SAGE_ROOT/local/bin were marked as parented to the 4.6.rc0 revision of the hg repository for some reason. Thus $SAGE_ROOT/local/bin/sage-banner had been replaced with the 4.6.rc0 banner. I had committed a revision to 4.6 before running sage -upgrade, so this may have somehow been responsible. Still, I'd appreciate it if someone else could test this.
I just took a vanilla, built-from-scratch, copy of Sage 4.6, ran "./sage -upgrade", and nothing changed for me. The banner is still the 4.6 banner, the Mercurial logs show no changes, and no new spkg's were installed.
Do you have any other sage programme running by the time you update? Maybe this would affect the process. But I don't think sage would actually "downgrade", but that might happen very rarely.
@pizza: I think that replying to comments that are 8 years old is probably not helpful. This one in particular deals with upgrading Sage, a procedure that has changed dramatically since version 4.6 in 2010.