On 25 Aug., 13:20, Keshav Kini <keshav.k...@gmail.com> wrote: > Mercurial versions in Sage haven't changed between 4.7 and 4.7.1. In any > case, incompatible Mercurial repository formats won't cause the error > messages we're seeing here, afaik.
> > "There are uncommitted changes in the Sage root repository. Aborting." I cannot find this message (apparently originating from Sage, not Mercurial) either, at least not in 4.7.2.alpha2's nor 4.7.1.rc2's root repo spkg-install; uncommitted changes (if any) should just get checked in, and if that failed for some reason, there would be a different error message. [Deleting the existing repo in $SAGE_ROOT/ prior to upgrading should also work, though that isn't very nice. Note that file mode changes won't be shown by 'hg diff' by default; this requires 'hg diff -- git'.] > If I recall correctly, `sage -upgrade` > does seem to complain about "uncommitted changes" even if there are files > which aren't even added yet, such as Kevin's > sage/rings/finite_field_givaro.pyx (which doesn't exist in a vanilla 4.7 or > 4.7.1 sage distribution). Wonder where that came from. > > Anyway I wouldn't recommend using `sage -upgrade` if you can avoid it. I wouldn't say that. We've improved upgrading such that it is now really meant to work, and we regularly test this.(Unfortunately Jeroen decided to no longer support upgrades *from* devel versions, which previously also worked.) I must admit I couldn't follow or finally review the ticket introducing the root repo w.r.t. upgrading though. Anyway, if upgrading (at least from final releases to new final releases) is broken for someone, this should be reported and get fixed. -leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
