[Python-apps-team] Bug#636396: mercurial: Cloning fails with: mpatch.mpatchError: patch cannot be decoded

[Javi Merino]

severity 636396 serious
forwarded 636396 http://mercurial.selenic.com/bts/issue2877
thanks

On 12/08/11 12:08, Nicola wrote:
> The reported error might be not directly related with python 2.6/2.7
> or the unstable version of mercurial:
> 
> I'm guessing that the original bug report caontained output of
> mercurial run on ARM architecture (my guess is that sheeva stands for
> sheevaplug), compiled with the "recently" updated gcc 4.6.1 toolchain.

Yes, I've reproduced this in another ARM machine.  mercurial is totally
unusable on armel right now.

> Apparently problems have been reported even for the stable version of
> mercurial when compiled with gcc 4.6.1 ARM toolchain:
> http://mercurial.selenic.com/bts/issue2877
> 
> I myself get exactly the same traceback reported in the original bug
> report and in the upstream one, when running any operation (clone,
> log, verify) using mercurial on debian ARM after a recent update that
> brought mercurial 1.8.3 and the gcc 4.6.1 toolchain.
>
> I would suggest revising the priority/severity of this bug (in the
> scope of armel architecture) as it seems to me that, at least on
> armel, the new packages are completely useless as any operation on new
> and preexisting repositories fails with this error.

Agreed.

> I'm not using any third party extension, nor any extension not
> included in the official bundle, and even disabling any extension the
> bug persists.

Yes, the same happens to Mel and me.  I'll try to debug this in the next
week now that I can reproduce it, but please chip in in the upstream bug
report if you have any suggestions.

Cheers,
Javi (Vicho)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20110813/42138e68/attachment.pgp>