[issue2228] transplant --continue aborts with "no node"

[Matthew Wild]

New submission from Matthew Wild <mwild1 at gmail.com>:

matthew at silver:~/prosody-scram-hash$ hg transplant -s ../prosody-hg-
jefferai -b scram-hash -a -p 847ec558f463 -p cf99fbcb8bef -p 75c962d1a389
  searching for changes
  applying 5fd1cb9995d6
  patching file core/usermanager.lua
  Hunk #2 FAILED at 20
  1 out of 2 hunks FAILED -- saving rejects to file core/usermanager.lua.rej
  patch failed to apply
  abort: Fix up the merge and run hg transplant --continue

I merged manually, and under instruction:

  matthew at silver:~/prosody-scram-hash/core$ hg transplant --continue
  abort: 00changelog.i at a74096f4fdff: no node!

I eventually noted that a74096f4fdff was a commit that only existed in the 
repository I was transplanting /from/ - and that running "hg transplant -s 
../prosody-hg-jefferai --continue" worked.

I'm unsure whether this is a UI or a transplant bug (should transplant 
remember where the current transplant operation is pulling from?).

----------
messages: 12766
nosy: MattJ
priority: bug
status: unread
title: transplant --continue aborts with "no node"

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2228>
____________________________________________________