Hash mismatch for Mercurial repo (`guile-wisp`)

Hi @ardumont @anlambert,

I notice this mismatch when downloading from the Vault:

SWH: found directory
with nar-sha256 hash c98bd6991721d60b9a79600428bfbe8db0aaac3d383cd2df803ed7867c7cb63b
at 'swh:1:dir:218d95849f10fc0691d7dfa80999ce5061e654ef'
swh:1:dir:218d95849f10fc0691d7dfa80999ce5061e654ef/
...
swh:1:dir:218d95849f10fc0691d7dfa80999ce5061e654ef/wisp.py
r:sha256 hash mismatch for /gnu/store/7pcac04x82wyhknyfkdwhk3j958n2r75-guile-wisp-1.0.7-checkout:
  expected hash: 0fxngiy8dmryh3gx4g1q7nnamc4dpszjh130g6d0pmi12ycxd2y9
  actual hash:   0z7y487nnmw22xry82bb75shwp50gacm4kbwn01vhhli2bchpx37

Well, if I download the nar-sha256 ExtID content c98bd6991721d60b9a79600428bfbe8db0aaac3d383cd2df803ed7867c7cb63b then the git-sha1 SWHID seems swh:1:dir:1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe.

# nar-sha256 Guix check
$ guix hash -S nar -f nix-base32 -H sha256 /gnu/store/7pcac04x82wyhknyfkdwhk3j958n2r75-guile-wisp-1.0.7-checkout
0fxngiy8dmryh3gx4g1q7nnamc4dpszjh130g6d0pmi12ycxd2y9

# nar-sha256 ExtID
$ guix hash -S nar -f hex -H sha256 /gnu/store/7pcac04x82wyhknyfkdwhk3j958n2r75-guile-wisp-1.0.7-checkout
c98bd6991721d60b9a79600428bfbe8db0aaac3d383cd2df803ed7867c7cb63b

# git-sha1 SWHID
$ guix hash -S git -f hex -H sha1 /gnu/store/7pcac04x82wyhknyfkdwhk3j958n2r75-guile-wisp-1.0.7-checkout
1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe

This SWHID returns something that looks good. Let's cook it, download, and extract.

# git-sha1 SWHID
$ guix hash -S git -f hex -H sha1 swh:1:dir:1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe
1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe

# nar-sha256 ExtID
$ guix hash -S nar -f hex -H sha256 swh:1:dir:1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe
c98bd6991721d60b9a79600428bfbe8db0aaac3d383cd2df803ed7867c7cb63b

# nar-sha256 Guix check
$ guix hash -S nar -f nix-base32 -H sha256 swh:1:dir:1f35a460673e2c8ccf948b8c18cb8c18d2ec24fe
0fxngiy8dmryh3gx4g1q7nnamc4dpszjh130g6d0pmi12ycxd2y9

I do not know yet if the issue is on your side, i.e, the nar-sha256 of ExtID associated to the incorrect git-sha1 SWHID. Or if the issue come from our side.

Cheers, simon