17200+ entries in 0.023s
mod6: are these the only two implemented thus far?
mod6: i'll give it a go as soon as I get the soba out and test the PVS.
mod6: heheh "Now Taste The Meat."
mod6: nice asciilifeform!
mod6: sure thing, sounds good.
mod6: i've got a release vpatch up my sleeve, but no email ready for that or anything. that's coming within a number of days I suspect. but probably after the 1st.
mod6: feel free to send what you like as far as tinyscheme.
mod6: asciilifeform: oh sorry, yeah, about to upload the stuff to the site & then send the emails.
mod6: ok all automated tests for V passed.
mod6: but yah, if all final tests work that include those patches, we're frozen and headed for a release.
mod6: i haven't even touched it yet.
mod6: i need to test PVS a bit more actually tho.
mod6: in your opinion, should the release include any of the three (from recent): PVS, Malleus, or High/Low-S ?
mod6: which is a good thing that the test picked it up.
mod6: all automated tests should pass now that we have your new PVS seal in the mirror ; was failing lastnight because V thought it was 'WILD', and it expected it to be signed by you.
mod6: it'll contain the fix from yesterday about the strictness of one of my regex's when matching up seals to vpatches; the change to look for the .wot dir in the current working directory by default (as well as .seals); and lastly has the post-press hash checker function also.
mod6: well, hoping to anyway.
mod6: im about to publish V [v99996] tonight.
mod6: ok good deal. feel free to fire off whatever you like at the ML, just be aware that we may have to re-process the vpatches post-release. that's all. salud.
mod6: does that make sense?
mod6: ok you should probably wait to run vdiff against the changes until i've got the release patch out then, so you can start from there.
mod6: im thinking that i'm gonna tag the release, and publish the release patch soon. just hoping that if any of it touches trb, that it'll be post-release patch so there are no conflicts.
mod6: (so far, i didn't see any that did)
mod6: does any of it touch any of trb's files?
mod6: you think it'll be useful at all before we release?
mod6: ok all set -- looking good.
mod6: ok stand-by, going to update the mirror.
mod6: <+ascii_butugychag> hm, then will try it again tonight << ok cool. got it.
mod6: <+ascii_butugychag> mod6: i actually re-sent a correct one last night, it vanished. << oh the entire message was snarfed?
mod6: shinohai tried to play with the command line flags but had some trouble. this isn't resolved yet. i was going to try those out myself, but I have had other fish to fry first.
mod6: i think it will, as long as I can get it tested. i haven't played with that one at all, other than compiling and running with it -- gives a version of 99999 by default.
mod6: asciilifeform: when you get a chance tonight or whatever, try to send through a correctly named sig for: 'asciilifeform-programmable-versionstring.vpatch' plz
☟︎ mod6: and again, i have no way of telling if they were named correctly in the first place or it was the ML. but... its certainly something that should be in a log file or something, you may wanna have a look.
mod6: im not sure what happend just now with the re-submits that alf did, one made it through ok, the other did not.
mod6: but these didn't come through like that. it's missing the 'asciilifeform' between 'vpatch' and 'sig'.
mod6: asciilifeform_malleus_mikehearnificarum.vpatch.asciilifeform.sig
mod6: asciilifeform-programmable-versionstring.vpatch.asciilifeform.sig
mod6: they should have signatures that are named as follows:
mod6: jurov: the original emails -- either asciilifeform named them incorrectly or the email server munged the names.
☟︎ mod6: mircea_popescu: yah, im more inclined to just wait until a new sig, properly named is sent.
mod6: haha, it's like trying to get one through the golies legs.
mod6: in the mean time i'll update the mirror with the good sig from malleus
mod6: you wanna roll the dice and see if you can get one through for PVS that isn't mangled? or should we wait for jurov?
mod6: well, we've got a well-named sig for malleus
mod6: changing the signature file name doesn't actually change the signature - but i was just hoping to get 'em both in the ML for posterity
mod6: thought it was just a oversight or something.
mod6: yeah, you're right. it hosed it.
mod6: yup np. all of your others have been 100% accurate.
mod6: Name: asciilifeform-programmable-versionstring.vpatch.sig
mod6: Name: asciilifeform_malleus_mikehearnificarum.vpatch.sig
mod6: mv asciilifeform-programmable-versionstring.vpatch.sig asciilifeform-programmable-versionstring.vpatch.asciilifeform.sig
mod6: mv asciilifeform_malleus_mikehearnificarum.vpatch.sig asciilifeform_malleus_mikehearnificarum.vpatch.asciilifeform.sig
mod6: here's what I had to do to each:
mod6: there are mangled names in just about every email for se
mod6: it's just those two sig files ya.
mod6: so im highly tempted to actually just rename the seal files in the mirror for Programmable Version Strings and the Malleus Mikehearnificarum, but will resist. you should probably just re-post as annoying as that may seem.
mod6: but, the good news is, other than those little hiccups, i think it would have been fine.
mod6: but I have this for you to review:
mod6: however, yeah, as you noted, your patches dont press out probably quite right because of the timestamps
mod6: i have fixed it in my forthcoming v99996, and this shouldn't be a problem any more.
mod6: and its because of one line that i'm not being strict enough with my regex.
☟︎ mod6: so yes, if I drop those into my patches dir with a full sync with V [v99997] it does indeed break my seal validation.
mod6: but moving on to your tinyscheme stuff...
mod6: anyway... thats just an fyi
mod6: I just noticed this now. And the sig verifies just fine, but yah. mis-named in the email so that threw me off a bit.