#10594: Upgrade to mercurial 1.7.3
-------------------------------+--------------------------------------------
Reporter: ryan | Owner: tbd
Type: task | Status: closed
Priority: major | Milestone: sage-4.6.2
Component: packages | Resolution: fixed
Keywords: mercurial | Author: Ryan Grout
Upstream: N/A | Reviewer: Dan Drake
Merged: sage-4.6.2.alpha2 | Work_issues:
-------------------------------+--------------------------------------------
Comment(by jhpalmieri):
After some issues on #9433, I wonder if this should be reopened. There
are some incompatibilities between Mercurial 1.7.3 and earlier versions;
see
[http://mercurial.selenic.com/wiki/UpgradingMercurial#Upgrading_and_downgrading_repository_formats
this web page]. I think the issues is this:
- any new repositories created with 1.7.3 (without including a flag like
`--config format.dotencode=False`) will not be usable by versions before
1.7.
I think a reasonable argument could be made for merging 1.7.3 anyway: when
dealing with Sage, it's not a huge requirement to ask people to use the
Mercurial distributed with Sage instead of some older version installed
elsewhere on their machine.
But perhaps a reasonable argument could be made on the other side: why
create repositories which can't be read by Mercurial 1.6.4 or earlier?
Should we back out 1.7.3 altogether?
We could also keep 1.7.3 but require all repos to be created with the flag
`--config format.dotencode=False`. I personally think that this is
unwieldy.
Any opinions?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10594#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
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-trac?hl=en.
