Freshly cloned Kallithea repository is corrupt

Mads Kiilerich mads at kiilerich.com
Mon Apr 17 11:39:59 UTC 2023


Hi

That seems to be a Mercurial 6.4 regression, introduced by 87f0155d68aa .

Can you confirm, and will you follow up upstream?

/Mads


On 17/04/2023 03:10, Manuel Jacob wrote:
> When I cloned the Kallithea repository, it was corrupted.
>
> % hg clone https://kallithea-scm.org/repos/kallithea /tmp/kallithea
> applying clone bundle from 
> https://kallithea-scm.org/bundles/kallithea-b103f41a4954e2814dc547671771bdeebc1f80be.bzip2-v1.hg
> adding changesets
> adding manifests
> adding file changes
>
>
> added 5838 changesets with 24921 changes to 6256 files
>
>
> finished applying clone bundle
> searching for changes
> adding changesets
> adding manifests
>
>
> adding file changes
> added 2930 changesets with 10026 changes to 634 files (+1 heads)
> 56305 new obsolescence markers
> new changesets abc1ada59076:0a9ddb8cd8c1
> 5838 local changesets published
> updating to branch default
> 567 files updated, 0 files merged, 0 files removed, 0 files unresolved
> % cd /tmp/kallithea
> % hg summ
> parent: 8765:b2c3d4568a5f
>  Merge stable
> branch: default
> abort: 00manifest at 47652662ac23c386e873c20b84f6aace9cca8bb5: no node
> % hg up default
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> % hg up stable
> abort: 00manifest at 47652662ac23c386e873c20b84f6aace9cca8bb5: no node
>
> I tried with both hg 6.4 and 6.4.1 (from different machines).
>
> Disabling clone bundles (`--config ui.clonebundles=false`) fixed the 
> problem.
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general




More information about the kallithea-general mailing list