Ok, just got back to my computer. Yes, that setting did the trick, although the script still doesn't work. Apparently this does not work for local repo-to-repo pulls?! But if I run it against hg serve or even via ssh://localhost, then it works with this setting and that's what I really need.
I had a quick look, but that item really isn't mentioned on *hg help -e clonebundles*. Probably should be. Thanks for your help. Seb On Mon, 7 Nov 2022 at 20:27, Sebastian Unger <sebunge...@gmail.com> wrote: > > > On Mon, 7 Nov 2022, 19:48 Mathias De Maré, <mathias.dem...@gmail.com> > wrote: > >> >> >> On Sat, Nov 5, 2022 at 11:27 PM Sebastian Unger <sebunge...@gmail.com> >> wrote: >> >>> BTW, here's a shell script with a minimal example of what I have. I >>> expect the clone --pull at the end to do a number of partial pulls rather >>> than pulling it all in one go. I have also tried running hg serve in the >>> server repo and pulling using http://localhost:8000 from the client. >>> Results were the same. >>> >>> *CAUTION*: The script will silently delete and recreate a >>> directory /tmp/hg-pbundles.tmp. >>> >> >> Based on what I see in your script, I think you're missing the >> server-side hgrc setting: >> [server] >> pullbundle = True >> >> $ hg help config.server.pullbundle >> "server.pullbundle" >> When set, the server will check pullbundles.manifest for bundles >> covering the requested heads and common nodes. The first matching >> entry will be streamed to the client. >> > Brilliant, thanks. I'll try that as soon as I get back to my computer. > > I was only reading the help on the clone bundles extension. I don't think > this item is mentioned there, or at least I did not notice it. > > Might be worth adding a reference there. > > >> For HTTP transport, the stream will still use zlib compression for >> older clients. >> >>> >>> On Sun, 6 Nov 2022 at 10:22, Sebastian Unger <sebunge...@gmail.com> >>> wrote: >>> >>>> No responses at all? Is this the right place for the question or should >>>> I post it somewhere else? Is any additional information needed? BTW, the hg >>>> version is 6.2.3 on both server and client. >>>> >>> >> This is the right place, but at least for me, I was on holiday, so no >> time to reply ;-) >> > Hope you had a good time! Again thanks! > > >> Greetings, >> Mathias >> >>> >>>> I'd really appreciate any help or hints. Or even just a report from >>>> someone who has pull-bundles working to know that it *can* be made to >>>> work. >>>> >>>> Cheers, >>>> Seb >>>> >>>> On Sun, 30 Oct 2022 at 23:11, Sebastian Unger <sebunge...@gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I've spent most of the weekend trying to enable the clonebundles >>>>> extension on our mercurial server. Setting up clonebundles was actually >>>>> fairly straightforward and seems to be working. >>>>> >>>>> However, since many of our users (me included) often only clone the >>>>> default branch and then selectively pull branches when needed and strip >>>>> when no longer needed, I would like to also set up pullbundles. >>>>> >>>>> However, so far I have had no luck with that one. Or at least I have >>>>> not noticed any differences from before: server load still goes up while >>>>> pulling a large branch and I have not noticed the multiple repeated pulls >>>>> as described in the clonebundles help. >>>>> >>>>> Here's the config for one of the smaller repos: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *hg@test-server:~/repos/hgadmin$ cat .hg/pullbundles.manifest >>>>> pullbundles/8312c21ae25993e6e0ef066913d8b4ba984557b56d0be230898a9a73493d5246.hg >>>>> BUNDLESPEC=zstd-v2 >>>>> heads=2df5f4368abf5f681421f80b142914c685189a8dpullbundles/651c2d609501fd1848cda07543a2e8449daaae6c0826e3323ef27ccaa7eddf53.hg >>>>> BUNDLESPEC=zstd-v2 heads=f146e48c486131e75102e0672064269a15310066 >>>>> bases=d02e13f7603e1fca280292aa7cca8ca4ff0deab3;39c4feaeabbbc7e24745635f266c477d8fe6e87dpullbundles/c57891cc34d7e7ba96b096f6c1990e803db9ecda7f0bd1e6df0f635d19c22c67.hg >>>>> BUNDLESPEC=zstd-v2 heads=73bf821c6a165b9862222fbedd12a87caf6c6dac >>>>> bases=f6266e0edb354090bea3a9a886fba987d2764686pullbundles/a94e641dd56e2c91cb025edcd0e3c27d9ec1b914e05926721ab6b075f381703d.hg >>>>> BUNDLESPEC=zstd-v2 heads=c307f4b0d1d0dce014ace5dcc839d406ac508f62 >>>>> bases=44ede9353dedd19418385e822b8aa4cc28468815pullbundles/09fa420d741a8424471ad08b6d0d64ddfd9567bc379ac3d58e64409926036264.hg >>>>> BUNDLESPEC=zstd-v2 heads=c60b324e4a2760507da87774dd029100d0315907 >>>>> bases=6c13274b16bb646b9793819d44ad515641a2e3d2hg@test-server:~/repos/hgadmin$ >>>>> ls -l .hg/pullbundlestotal 316-rw------- 1 hg nogroup 1963 Oct 30 21:53 >>>>> 09fa420d741a8424471ad08b6d0d64ddfd9567bc379ac3d58e64409926036264.hg-rw------- >>>>> 1 hg nogroup 6162 Oct 30 21:53 >>>>> 651c2d609501fd1848cda07543a2e8449daaae6c0826e3323ef27ccaa7eddf53.hg-rw------- >>>>> 1 hg nogroup 302064 Oct 30 21:53 >>>>> 8312c21ae25993e6e0ef066913d8b4ba984557b56d0be230898a9a73493d5246.hg-rw------- >>>>> 1 hg nogroup 559 Oct 30 21:53 >>>>> a94e641dd56e2c91cb025edcd0e3c27d9ec1b914e05926721ab6b075f381703d.hg-rw------- >>>>> 1 hg nogroup 861 Oct 30 21:53 >>>>> c57891cc34d7e7ba96b096f6c1990e803db9ecda7f0bd1e6df0f635d19c22c67.hg* >>>>> >>>>> Can somebody spot something I'm missing? Do I need to configure or >>>>> enable anything on the clients? Is pullbundles even expected to work? >>>>> >>>>> Cheers, >>>>> Seb >>>>> >>>> _______________________________________________ >>> Mercurial mailing list >>> Mercurial@lists.mercurial-scm.org >>> https://lists.mercurial-scm.org/mailman/listinfo/mercurial >>> >>
_______________________________________________ Mercurial mailing list Mercurial@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial
