[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

different .diff.gz for different platforms (armel) prohibiting upload



Hello,

my non-free package mgltools-molkit built nicely everywhere, but the armel
could yet not be uploaded - blocking the autodocktools to arrive in testing.

I tried to help it out with my OpenMoko running Debian, and while it builds, I
cannot upload since the .diff.gz generated by dpkg-buildpackage -sd is not
bit-identical to the .diff.gz that is in the archive. The unpacked diff.gz
however _is_ identical. You then the the .dsc and the .changes to disagree with
the various checksums.

I have performed the armel-builds and uploads for a series of other mgltools-*
packages, hence while the error may be on my side, I would be somewhat surprised.

Is there a standard procedure to follow? Shall I somehow (how?) invoke
dpkg-genchanges manually with the .diff.gz being exchanged with the original
again? Is there some other trick of the trade?

And: if my error report is correct, is the logic possibly flawed to reject the
upload even though the contents of the .diff.gz are identical?

$ LANG=C diff mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz && echo identical ||echo differ
Binary files mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz and
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz differ
differ

now with zdiff:

$ LANG=C zdiff mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz && echo identical ||echo different
identical


Many thanks

Steffen

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: