Red Hat Bugzilla – Bug 1006457
Mercurial doesn't add broken symlink when using "copy -A"
Last modified: 2015-07-22 03:45:42 EDT
Description of problem:
Broken symbolic links are not added like they should be when "copy -A" is used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
ln -s file.txt link_valid.txt
ln -s nothing.txt link_invalid.txt
hg add dir
hg ci -m "Initial checkin"
mv dir moved
hg copy -A dir/file.txt moved/file.txt
hg copy -A dir/link_valid.txt moved/link_valid.txt
hg remove dir/file.txt
hg remove dir/link_valid.txt
hg copy -A dir/link_invalid.txt moved/link_invalid.txt
hg remove dir/link_invalid.txt
moved/link_invalid.txt is not added to the repository.
moved/link_invalid.txt should be added to the repository.
I noticed that version 1.4.3 of Mercurial is available, so I tested to see if the issue was fixed in that version, but it is not.
Also, potentially worth noting is that I did the above test on RHEL 5 (which uses Mercurial 1.3.1) and the same issue exists there as well.
Created attachment 797388 [details]
Source rpm of Mercurial 1.4.3 with patch to fix the broken symbolic link issue
The fix that this patch is taken from can be found at:
I also noticed that Mercurial 1.4.3 is available, so I tested this patch applied to that updated source and it resolves the issue.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
This is still an issue and I'd like to request that it be considered that the fix be included in the next release.
Created attachment 954862 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.