Bug 3212 - Abort during merge
Summary: Abort during merge
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: unspecified
Hardware: All All
: normal bug
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 04:46 UTC by Jan Sorensen
Modified: 2012-05-13 04:50 UTC (History)
4 users (show)

See Also:
Python Version: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Sorensen 2012-01-18 04:46 UTC
I have a problem with a merge that aborts with an error. I have two changesets, in one 'x' is a symlink and in the 
other a normal file. If I merge the symlink changeset into the changeset where 'x' is a normal file, the merge 
command will abort with:

   abort: could not symlink to '': No such file or directory: /tmp/repo/x

Note that the merge works if the merge is the done in the other direction. It will then (as I expect) prompt to take 
local or other.

The problem can be demonstrated with the following command sequence.

$ hg init
$ touch target
$ hg com -Ambase
adding target
$ ln -s target x
$ hg com -Amlink
adding x
$ hg update 0
$ touch x
$ hg com -Amfile
adding x
created new head
$ hg merge

The problem is with 2.0.2 on Linux
Comment 1 Matt Mackall 2012-01-26 20:44 UTC
Turns out this is a duplicate of issue3200, closing.
Comment 2 Bugzilla 2012-05-12 09:27 UTC

--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:27 EDT  ---

This bug was previously known as _bug_ 3211 at http://mercurial.selenic.com/bts/issue3211