Hi Simon,
On Tue, Feb 9, 2010 at 1:20 AM, Simon King wrote:
> Hi!
>
> I just upgraded sage 4.3.1 to sage 4.3.2. In sage 4.3.1, there were a
> couple of patches (from various tickets), but I went back to the
> unpatched state, by hg_sage.update(originalversionnumber).
The problem is probably due
I had a similar problem, in a directory where I had not applied any
patches previously, so it seems like a problem with 4.3.2. I actually
randomly answered no and yes, whichever allowed me to finish the
upgrade. No problems so far, but I'd like to know what the possible
consequences are, too. O
Hi!
I just upgraded sage 4.3.1 to sage 4.3.2. In sage 4.3.1, there were a
couple of patches (from various tickets), but I went back to the
unpatched state, by hg_sage.update(originalversionnumber).
During the upgrade, I was notified that some of the patches seemed to
be previously applied, and wa
