#3052: mercurial --> plain text --> mercurial
----------------------------+-----------------------------------------------
Reporter: was | Owner: mabshoff
Type: defect | Status: positive_review
Priority: major | Milestone: sage-4.7.2
Component: distribution | Keywords:
Work_issues: | Upstream: N/A
Reviewer: Volker Braun | Author: Keshav Kini
Merged: | Dependencies: #10594
----------------------------+-----------------------------------------------
Description changed by leif:
Old description:
> Robert Bradshaw has mostly solved this:
> {{{
> I've looked into this some more and it looks like we can completely
> reconstruct a repository from the export of all its keywords. The
> trick is to use the --exact keyword when importing. This forces it to
> apply the given patch to the correct parent (sometimes creating a new
> head) and will also correctly import merge patches (removing heads).
> Some scripts to do this are up at
>
> http://sage.math.washington.edu/home/robertwb/hg/
>
> I've successfully exported and re-created simple repositories (with
> branching) with these scripts, and it works great and preserves all
> the history. The only issue is that I can't seem to get it to work
> with any repositories older than a certain date. I think the issue is
> that mercurial changed the way nodeid's are calculated (and I keep
> getting an error "abort: patch is damaged or loses information" which
> is thrown when the newly computed nodeid does not match the one in
> the patch (command.py:1632 in 0.9.5)). Matt Mackall, any suggestions
> on how to cleanly get around this/get the old node-id numbers instead?
>
> - Robert Bradshaw
> }}}
>
> But there are issues. See the complete thread here:
>
> http://groups.google.com/group/sage-
> devel/browse_thread/thread/79da4852b8e20851/c4b8e87260f08f96?#c4b8e87260f08f96
>
> Apply
> * trac_3052-makefile.patch to $SAGE_ROOT
> * trac_3052-textify.patch to the base repo ($SAGE_ROOT/spkg/base)
New description:
Robert Bradshaw has mostly solved this:
{{{
I've looked into this some more and it looks like we can completely
reconstruct a repository from the export of all its keywords. The
trick is to use the --exact keyword when importing. This forces it to
apply the given patch to the correct parent (sometimes creating a new
head) and will also correctly import merge patches (removing heads).
Some scripts to do this are up at
http://sage.math.washington.edu/home/robertwb/hg/
I've successfully exported and re-created simple repositories (with
branching) with these scripts, and it works great and preserves all
the history. The only issue is that I can't seem to get it to work
with any repositories older than a certain date. I think the issue is
that mercurial changed the way nodeid's are calculated (and I keep
getting an error "abort: patch is damaged or loses information" which
is thrown when the newly computed nodeid does not match the one in
the patch (command.py:1632 in 0.9.5)). Matt Mackall, any suggestions
on how to cleanly get around this/get the old node-id numbers instead?
- Robert Bradshaw
}}}
But there are issues. See the complete thread here:
http://groups.google.com/group/sage-
devel/browse_thread/thread/79da4852b8e20851/c4b8e87260f08f96?#c4b8e87260f08f96
----
Apply [attachment:trac_3052-makefile.patch] to the '''Sage root'''
repository (in `$SAGE_ROOT/`).
Apply [attachment:trac_3052-textify.patch] to the '''base repository'''
(in `$SAGE_ROOT/spkg/base/`).
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3052#comment:9>
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.
