I don't think 4.6.2.alpha1 -> 4.7 or 4.6.2.alpha1 -> 4.7.alpha2 would work,
unless 4.6.2.alpha1 was released before Jeroen started his history-rewriting
prereleases. Essentially each new version (prerelease or otherwise) is
created by *backtracking to the latest stable release and readding all t
On Friday, May 27, 2011 10:24:59 AM UTC-7, Nils Bruin wrote:
>
> I tried a "sage -upgrade" on a pristine 4.7.rc4 install to get to 4.7
> and I got hg "unresolved" and "uncommitted changes" problems left and
> right. Since "sage -upgrade" duly warns that it offers no guarantees,
> that's not re
I tried a "sage -upgrade" on a pristine 4.7.rc4 install to get to 4.7
and I got hg "unresolved" and "uncommitted changes" problems left and
right. Since "sage -upgrade" duly warns that it offers no guarantees,
that's not really a bug, but given that I didn't do anything with that
4.7.rc4 other than
On May 26, 1:29 am, Jeroen Demeyer wrote:
> > File "/usr/local/sage/4.7/devel/sage/sage/tests/cmdline.py", line 198:
[...]
> > Got:
> > 'ERROR: history is not a magic function\n'
>
> Is it reproducible if you run ./sage -t devel/sage/sage/tests/cmdline.py
> several times?
Yes it is
> Did the
