[Bug 4018] New: Cloning subrepos from a network drive to a network drive fails

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Mon Aug 12 14:10:37 CDT 2013


http://bz.selenic.com/show_bug.cgi?id=4018

          Priority: normal
            Bug ID: 4018
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Cloning subrepos from a network drive to a network
                    drive fails
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: sade at avr-vr.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.7
         Component: Mercurial
           Product: Mercurial

I have a repository located on a network drive that contains subrepos. I can
clone this repository successfully to any of my local drives, and the subrepos
get cloned as they should. I can also clone from my local drive to the network
drive.
However, for some reason, the clone fails if I do it from the network drive to
the network drive.


Here are some quick steps to reproduce it:
Notes:
-W:\ is a network drive; I also tried using the \\full\unc\path in the hg
commands, to no avail

----------------------------------------------------

------Setup main repo
W:\>hg init test
W:\>cd test

------Setup subrepo
W:\test>hg init sub
W:\test>cd sub
W:\test\sub>echo blah>dummy.txt
W:\test\sub>hg add
adding dummy.txt

W:\test\sub>hg commit -m "Dummy commit"

------Just to check the changeset number of this...

W:\test\sub>hg tip
changeset:   0:daba732e061a
tag:         tip
user:        sade
date:        Mon Aug 12 14:45:57 2013 -0400
summary:     Dummy commit

W:\test\sub>cd ..

------Add subrepo to mainrepo

W:\test>echo sub = sub>.hgsub

W:\test>hg add .hgsub

W:\test>hg commit -m "Added subrepo"

W:\test>cd ..

------Attempt to clone from W:\test to W:\test2

W:\>hg clone test test2
updating to branch default
cloning subrepo sub from W:/test/sub
abort: unknown revision 'daba732e061a3eaea1438d79faf6e0a1c1223c8e'!

------Clone from W:\test to C:\test-clone

W:\>hg clone test C:\test-clone
updating to branch default
cloning subrepo sub from W:/test/sub
2 files updated, 0 files merged, 0 files removed, 0 files unresolved

----------------------------------------------------

So, notice how the clone aborted with 'unknown revision', even though it
clearly is the subrepo's revision, which does exist.
Also notice how the second clone to a local drive worked fine.

Ugly workaround: clone to a local drive, then cut-paste the repo to the network
drive?

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


More information about the Mercurial-devel mailing list