log☇︎
47100+ entries in 0.362s
asciilifeform: ( and phf prolly also, he has a convenient place for this )
asciilifeform: anyone who considers self a 'graduate' of ch1, i.e. having loaded it Into Head, is invited to sign the genesis.
mircea_popescu: yes, perfect properties to make a subtle bug
asciilifeform: the genesis contained the clearsig. this did not choke vdiff, it ended up on the right side of a genuine +++ , there was no symptom of problem.
mircea_popescu: they utterly don't belong there. you got a .sig mechanism for this.
asciilifeform: i'ma upload a signed phf-cured second_cut presently, if no one can think of a reason not to
trinque: a better 1line
asciilifeform: this is not a solution.
mircea_popescu: idiotparser has the extreme advantage of not even being a parser, ie, simplicity.
mircea_popescu: and a rule whereby ada comments are "-- " not "--" is not the end of the world either.
asciilifeform: mircea_popescu: ideally not. this readme.txt however was made to stand alone, in a blog article, and hence contained clearsig.
mircea_popescu: asciilifeform you shouldn't put gpg clearsigned bits in a patch in the first place.
phf: you want me to write a second_cut by hand that presses cleanly?
phf: you can hand produce a second_cut that's not broken by tooling
phf: in this case "better parser" is a parser that actually understands the format it's processing
phf: _but it will require either writing a vdiff from scratch, or else adding a better parser to vdiff_
phf: but it will require either writing a vdiff from scratch, or else adding a better parser to vdiff
asciilifeform: phf: can you come up with a pill that doesn't break ada comments ?
asciilifeform: a great many of them.
phf: the problem is not diff or diff format, the problem is that vdiff does a naive grep for a prefix and breaks a perfectly valid traditional patch
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, ===.
a111: Logged on 2017-01-05 00:43 asciilifeform: incidentally you will blow up on the +++ mine if you try and diff a vdiff.
a111: Logged on 2017-12-06 21:46 mircea_popescu: we'll end up with a s/-/=/ intermediate step or wtf.
a111: Logged on 2017-12-06 22:05 phf: if you just run a diff -uNr on the two readmes, the resultant patch works. if you run a diff on the resulting patch and the vpatch in the tar, then you can see that there's something wrong with the vpatch specifically
phf: if you just run a diff -uNr on the two readmes, the resultant patch works. if you run a diff on the resulting patch and the vpatch in the tar, then you can see that there's something wrong with the vpatch specifically ☟︎
mircea_popescu: i suppose the third alternative is to actually implement a proper diff as part of vtron
trinque: who was? just trying a patch with bsd stubble vs gnu moss-hair
trinque: a read of the manfile of linux patch suggests *massive* fuckery to allow idjits to pull patches out of other text, email, newsgroups, etc
mircea_popescu: in that there's no reason to have them, and their presence is in itself sign of babbage's braindamage, much like say a canister for light, or a faucet for patience.
mircea_popescu: alternately, of course... "no clearsigned material within patches". this may even be a right thing independently of the actual bug.
mircea_popescu: we'll end up with a s/-/=/ intermediate step or wtf. ☟︎
mod6: <+asciilifeform> i recall a similar boojum in my 1st attempt at the FG release, that time it was a '+++' inside a uuencoded blob << lol, ok i see the problem too. you're right, this similar thing happened before.
asciilifeform: i recall a similar boojum in my 1st attempt at the FG release, that time it was a '+++' inside a uuencoded blob
mod6: crap, just a sec, haven't even looked yet. bbs.
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: 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: because i think i may have found a bug in diff
mircea_popescu: on a long enough timeframe, there's going to exist a vtron in ~any language anyway, i expect.
mircea_popescu: i'm not going to pick a wife for you, "here, THIS is the woman you should be comfortable with". pick your own. languages idem.
mod6: It /is/ a bit worrysome that I believe that I'm the only person who knows how it works. And since it's the only version in existence that encompasses all of the rules arbitrated in our chamber, that a new version that is easier to understand is warranted.
mircea_popescu: mod6 it's not a crime to have a perl vtron. however, if you plan as your own strategy to move away from perl and you're judging it more of a liability than anything, then by all means, eschew.
mod6: because what i don't want to do is have a perl genesis, then some vpatch that deletes everything and inflates a bunch of ada stuffs. prolly be better to start in the lang you expect to say within for the lifetime of the application.
trinque: mod6: makes sense, not vpatching a prototype
mod6: <+trinque> genesis doesn't have to mean perfect. <+trinque> nobody's going to come for you with pitchforks << no one expects a spanish something or other either...
asciilifeform: this is not the 1st time i plugged a finger into 220v. the breaker, i will however point out -- worked
trinque respectfully points out that at least by his eyes, V forces personal responsibility, not a pretense to being immaculately conceived.
mod6: Additionally, if someone in the republic wishes to create a vpatch/genesis and have a second pair of eyes look it over, by all means, send it to me.
mod6: I should have examined/tested your mpi vpatches, alf. I'll continue to try to be a second pair of eyes, reading them. There's no substitute for reading. For those following along, take note.
a111: Logged on 2017-12-05 17:47 asciilifeform: ( lessee if i properly ate & shat, 'i do not consider myself a programmer, for i have another craft. let's say i am an amateur programmer. and yet though i am an amateur, i find myself having written tens of thou. of loc in this-here life. and at least a min of 10k loc for web. but wanna hear sumthing ? never have i created a security hole in any. never. do you suppose i simply had good luck ? possibly luck. or possibly i wrote the c
mircea_popescu: now stop doing this inane shit, it's a significant drag on resources.
asciilifeform: but a genesis . all of the antecedents are 'false'
asciilifeform: the second_cut on my www -- is not a proper patch at all
mircea_popescu: asciilifeform> what means 'finished', it's a spoil of war artifact. << that's entirely not related to the discussion.
asciilifeform: mod6: in this case asciilifeform is quite puzzled why it appears to need a regrind; none of the file hashes should have changed
mod6: it can't check the expected sha of a patch BEFORE its DONE patching.
mod6: I had started a new V in Ada, had to stick it in the drawer for a while. Not getting to exactly where I wanted to go (easy to read, fits in head, no perl/perlisms) with it at this time.
asciilifeform: make a fresh working set, with no failed-press residue, and you will get a working press.
asciilifeform: what means 'finished', it's a spoil of war artifact.
mircea_popescu admires how the "finished" mpi managed to take a whole day of 3 people's time and shakes his head displeasedly.
diana_coman: is there now a problem with second_cut?
mod6: looks like second_cut might need a re-grind.
asciilifeform: ( a working vtron will immediately barf if encountering a file mismatching the claimed hash )
diana_coman: asciilifeform, thank you, I'll look in a minute; (had all hands full a minute here with all sorts)
asciilifeform: the issue is as fixed as it gets. i posted the grep item as example of how to verify, without even a vtron, that nothing has been slipped in from under the table.
asciilifeform: phf: if you had some code in your patch viewer to eat this type of horror, as 'special case', it is now a good time to throw it out
asciilifeform: diana_coman: plox to verify that this worx as described above, when you get a chance.
mircea_popescu: asciilifeform : "Lamport Parachute (a crypto identity bootstrap solution)"
asciilifeform: says 'are you sure this is a vpatch'
mircea_popescu: aaanyway, suppose diana_coman wants to add a patch to mod6's vtron, to better error messages
BingoBoingo opting out of major decisions until getting in a full sleep in. But, Haz uruguayan numero de telefono
asciilifeform: it's a straight formattingbug.
mircea_popescu: oh, it's a clerical problem only ?
mircea_popescu: asciilifeform just as soon as someone puts a patch on top of it, the trees will diverge and then phf can exclude the legacy one or w/e it is he does to them
mircea_popescu: sign a new genesis, abandon this one.
asciilifeform: or alternatively sign a cleaned genesis
asciilifeform: i can sign a vpatch of ~the genesis~ per se
asciilifeform: it contains simply a press
asciilifeform: i considered to ask 'a hundy of what' but decided not to
a111: Logged on 2017-12-06 14:10 mircea_popescu: http://btcbase.org/log/2017-12-05#1746620 << pretty sure i "accidentally"-ed a hundy or so at some point, look carefully through the couch cushions.
phf: asciilifeform: something like that. my btcbase vpatch grepper is dumb (it's my own eyes, but not the brain) and it's mostly just looking for things that look like a vpatch/vdiff. i definitely didn't unpack the first post tgz
asciilifeform: ( supposing this makes a difference )
phf: asciilifeform: i had issues specifically with an older, genesis-less version. my system doesn't require antecedents to be there, but for some reason when there's only one, antecedent-less patch it gives me a 404. i've not actually investigated, since you produced a genesis since
mod6: hi, looks like you've had some issues with my v : asciilifeform & diana_coman, I'll have to take a look at this later when I can. thx.
asciilifeform: diana_coman: do me a favour, tar up the entire thing
diana_coman: and I ran it : v99 --wot .wot --seals .seals patches a mpi_second_cut.vpatch
asciilifeform: ./v.pl a mpi_second_cut.vpatch
asciilifeform: at least oughta have a verbose mode one can optionally enable, wtf
asciilifeform: this VERY POSSIBILITY of silent failure is a bug, mod6
diana_coman: a gpg --verify here worked perfectly fine for me too on both patches
mircea_popescu: a ok\
asciilifeform: where it silently barfs on a signature and doesn't say why
asciilifeform: sounds like a bug in mod6's vtron, thus far
diana_coman: tch: Error! Could not find vpatch "mpi_second_cut.vpatch" ; when I run v a mpi_second_cut.vpatch I get: Error! Could not find vpatch "mpi_second_cut.vpatch"
mircea_popescu: ie, isn't a port from system with kbd-and-mouse, but actually designed / thought into the terms of a tapdevice.
asciilifeform: somehow in 'dream logic' it seemed entirely unsurprising that 'nam' were still a going concern.
mircea_popescu: asciilifeform so did you get nam over with by your own self or was there a sidekick ?
mircea_popescu: a did it ? i forgot too.
BingoBoingo: Well, i did forget it was a thing and underestimated how big a deal it would be until first leg of trip ended
mircea_popescu: by the time you crashland you're more or less CNCd into a ball already. just like an egg that was tumbled with rocks.