[Bug 3756] New: Creating a local clone results in an empty target repository
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Mon Jan 7 23:43:40 CST 2013
http://bz.selenic.com/show_bug.cgi?id=3756
Priority: normal
Bug ID: 3756
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: Creating a local clone results in an empty target
repository
Severity: bug
Classification: Unclassified
OS: Mac OS
Reporter: visagie at gmail.com
Hardware: Macintosh
Status: UNCONFIRMED
Version: 2.4.2
Component: Mercurial
Product: Mercurial
Using Mercurial 2.4.2 installed from the official package on Mac OS X 10.8.2,
and the Apple-supplied Python 2.7.2
Creating a local clone of a local repository succeeds, but the resulting target
is an empty Mercurial repository. Steps required to replicate the problem:
myhost:~/tmp$ mkdir foo && cd foo
myhost:~/tmp/foo$ echo "foo" > foo.txt
myhost:~/tmp/foo$ hg init
myhost:~/tmp/foo$ hg commit -m "test" -A
adding foo.txt
myhost:~/tmp/foo$ cd ..
myhost:~/tmp$ hg clone foo bar
no changes found
updating to branch default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
The source repository reports no problems when "hg verify" is used. There is
plenty of free disk space.
"clone --pull" doesn't work either, nor does changing into the target repo and
trying to do an hg pull manually.
Note that I CAN still use 2.4.2 to clone repositories created months or years
ago using much older versions of Mercurial. But attempting to clone
repositories created within the past few months (probably using 2.3.x) result
in empty targets.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list