The .hg directory created from the mozilla-central.hg bundle is much larger than the .hg directory created by a pull directly from mozilla-central. In my case on Mac and Linux the former uses 1.9 GB while the latter uses 670 MB.
So this seems to depend on the way the bundle is turned into a repository. I tried the following three methods (pull, unbundle and clone) with the following three results: # with mozilla-central.hg in the cwd: mkdir 1 2 ( cd 1 && hg init && hg pull ../mozilla-central.hg && du -sh .hg ) # 1.9 GB ( cd 2 && hg init && hg unbu ../mozilla-central.hg && du -sh .hg ) # 671 MB hg clone mozilla-central.hg 3 && du -sh 3/.hg # 674 MB So the problem only appears to exist when you use |hg pull|.
I'll report the problem with pull upstream, but it would also be great if someone could add a README.txt file to the bundle directory on ftp.mozilla.org noting how the bundles can be turned into a repository, and warning people away from using the pull command.
Summary: hg repo bundles create unexpectedly large repos → hg repo bundles create unexpectedly large repos when unbundled using |hg pull|
Summary: hg repo bundles create unexpectedly large repos when unbundled using |hg pull| → hg repo bundles create unexpectedly large repos when unbundled using the pull command
For anyone that's interested, the reason that the .hg directory created by the pull command is much larger for me is because there's a file .hg/hg-bundle-ttt7I7.hg10un [left?] in there that is 1.3 GB in size. So hopefully not to hard to fix manually if this has happened to you, or to fix upstream.
Currently using Mercurial 1.8.2.
Going to say WONTFIX here then, there's nothing for us to change in how we generate the bundles. Seems to be an hg problem.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
Filed http://mercurial.selenic.com/bts/issue2797 upstream.
I added http://ftp.mozilla.org/pub/mozilla.org/firefox/bundles/README.txt to point to our documentation on MDC.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.