[Bug 3606] New: mercurial convert extension incompatible with monotone 1.0

bugzilla-daemon at bz.selenic.com bugzilla-daemon at bz.selenic.com
Mon Sep 3 18:39:02 CDT 2012


          Priority: normal
            Bug ID: 3606
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: mercurial convert extension incompatible with monotone
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: devurandom at gmx.net
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.2.3
         Component: convert
           Product: Mercurial

$ hg --debug convert TheProject/ TheProject.hg                                  
running: 'mtn' 'automate' 'interface_version' '-d' 'TheProject/' < /dev/null
mtn automate version 13.0 - using automate stdio
running: 'mtn' 'automate' 'stdio' '-d' 'TheProject/'
mtn: misuse: '/home/TheUser/Projects/TheProject' is a workspace, not a database
mtn: misuse: (did you mean '/home/TheUser/.monotone/dbs/TheProject.mtn'?)
run hg sink post-conversion action
abort: mtn automate stdio header unexpected: 

$ hg --debug convert ~/.monotone/dbs/TheProject.mtn TheProject.hg
abort: /home/TheUser/.monotone/dbs/TheProject.mtn: not a Mercurial bundle

Using Mercurial 2.2.3 and Monotone 1.0.

I assume _MTN/options should be parsed and the database and branch be

$ cat TheProject/_MTN/options 
database "/home/TheUser/.monotone/dbs/TheProject.mtn"
  branch "TheBranch"
  keydir "/home/TheUser/.monotone/keys"

The other option might be to change the working directory to the source project
dir (i.e. the one containing _MTN) and letting monotone find the db on its own.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Mercurial-devel mailing list