asciilifeform: i'm also allears re: what a Properly Made vdiff oughta do. 'replace with ===' is not an answer, it simply creates a new magic death word, ===.
asciilifeform: ( instead it can only eat ones that dun contain '---' and '+++' and possibly other boojums )
asciilifeform: i'm all ears, phf . but my current understanding is that the problem is in that vdiff cannot eat arbitrary 7bitclean ascii files.
asciilifeform: some texts cannot be (!) vdiffed, for so long as we use unix diff; these appearently include gpg sigs
asciilifeform: i recall a similar boojum in my 1st attempt at the FG release, that time it was a '+++' inside a uuencoded blob
asciilifeform: ( observe that the sha512 sums of the readme in 'a' and 'b' match the ones given in the vpatch. but unix patch cannot actually make the patch happen. )
asciilifeform: the sad part is that i have nfi how to cure this , it is a consequence of using unix diff ( with in-band signal ) to begin with.
asciilifeform: i will not spoil the surprise , folx who look in the tarball will see what the caltrop was.
asciilifeform: there was no mistake in asciilifeform's procedure for baking the item. second_cut is in fact a patch, not a genesis, asciilifeform spoke hastily. there is also no bug in mod6's vtron, or in asciilifeform's. diana_coman did not make a mistake.
asciilifeform: mircea_popescu: at any rate, mod6 is right , i'ma have to regrind the 2nd patch. and also stuck , deservedly, with the chore of demonstrating that the payloads are unaltered.
asciilifeform: mircea_popescu: 9 of 10 occasions it is somebody else's bug!1
asciilifeform: the bigger problem is that nobody noticed.
asciilifeform: but a genesis . all of the antecedents are 'false'
asciilifeform: the second_cut on my www -- is not a proper patch at all
asciilifeform: phf how the hell did this get eaten by your vtron
asciilifeform: how come nobody bothered to look at second_cut with naked eye ?
