16200+ entries in 0.028s
mod6: so lastnight, I tested an updated version of the automated build script 'build-bitcoind-V99996.sh' -- the version that's currently deedbotted is no longer ok since I reground alfs patches.
mod6: <+mircea_popescu> hoping that mod6 will save you from inclusion arbitrarily is a lot fucking weaker than just having the proper control of only signing in the test branch, and choosing where yhou sign << yah, this may be a really good idea. right now, we're livin on the edge.
mod6: ok so that one line update built fine... good to know.
mod6: mircea_popescu: hows the power situation been?
mod6: heard reports from gernika, and shinohai
mod6: ok testing the one line change to v99996 build script.
mod6: my apologies, kinda thinking out loud here.
mod6: (this is without the makefiles), with the makefiles, we'll have to wait on the release vpatch until the makefiles are vified.
mod6: then we can update the build script for v99995 where it presses up through `v054-RELEASE.vpatch' or something.
mod6: so once the new V is out, i don't see why at that point we don't submit the release vpatch.
mod6: until caches expire, ya
mod6: where do you get A records if all of the root/gtld servers vanish?
mod6: these are the new root servers.
mod6: I did too, but we need more mirrors imho
mod6: anyway, so again, my short term goal here is to get V stablized so hopefully no further changes will be needed once i pt out v99995
mod6: mircea_popescu: you need any help, or did you get that issue with it dying sorted?
mod6: im trying to avoid getting hit over the head with "but it uses curl!" -- but maybe i like the beatings?
mod6: instead we just have a "release" version of the build script like everyone has been using and then push the "better build aparatus" into the post release development push.
mod6: im starting to think that maybe we dont worry about that for this release.
mod6: alright, well, we'll have to come up with something.
mod6: ok so you're not sold on these 'eh.
mod6: which everyone has said, needs to happen.
mod6: yeah, well, that is one of the things. we need to figure out where to pull the stuff from -- and again if locally, then we need to totally alter buildroot.
mod6: ah, ok. well, we're planning on working through these things. any other things?
mod6: how can it be better?
mod6: getting the makefiles squared away, is the last remaining task (other than regression testing) that stands in the way of v054
mod6: it basically breaks up my build script into makefiles. its worth your time to take a look i think.
mod6: asciilifeform: umm. not sure.
mod6: i just haven't quite figured out how im gonna fit it all together since they need to be Vified as well. at lesat, I think they do...
mod6: i was working on those lastnight, getting some stuff updated.
mod6: did you look at trinques makefiles?
mod6: then move on and there will just be a new version soon.
mod6: i guess I should make the script change and get it deedbotted.
mod6: Cause then I'm gonna release V v99995, which will require another script update.
mod6: well, we need to make a 1 line change to the 99996 build script, and then update the wiki. BUT on the other hand we're gonna need 99995 soon anyway, as soon as some people beat up on my latest patch for V.
mod6: danielpbarron, got plans this weekend?
mod6: ah, ok.. but don't run the 99996 yet -- the script needs a 1 line update iirc.
mod6: ah yes: ./v.pl p verbose TEST2 asciilifeform_add_verifyall_option.vpatch
mod6: i think this is how it is, and should be.
mod6: basically, either you accept the preposed in toto, or you do not and piece-meal it together by which people you trust and do not, and which patches you want or do not.
mod6: its a choose your own adventure really.
mod6: <+ben_vulpes> my mind recoils at the notion of running a reference implementation compiled without knowing the patchlist going into it << im not sure how to reconsile this. either you don't know what you're doing and you use a fully automated build script, or you do, and you build by hand.
☟︎ mod6: awe, poor perl. has no friends.
mod6: they could be better, sorry.
mod6: <+ben_vulpes> yes mod6's scripts are excellent, use them! << hey now!
mod6: ah, where can I find the source for that?
mod6: +++ b/bitcoin/src/main.cpp 02ccc72e42939509fc180861db7ffec50563a84869f35671fcf720090f9782674edcc89c4174175691566fac7277f1ebe0f50253d1e4a995eb960f5b43cce2a3
mod6: --- a/bitcoin/src/main.cpp 92038390413f77b55e19439738e87c21bd5b2313dc6edad78bcc8bf722dde82623a31a56a87b0182e75e6824fc709dc216fb9cb159b49a16e212e3a5ded93f58
mod6: diff -uNr a/bitcoin/src/main.cpp b/bitcoin/src/main.cpp
mod6: ben_vulpes: yeah, pretty close
mod6: huh. for some reason, it didn apply that patch
mod6: mircea_popescu: what's your sha512 of main.cpp?
mod6: but again, shouldn't effect Mr. P. since he did all of this before the regrind.
mod6: however, that's been out of date since I re-ground those recent patches.
mod6: when he built it, it ~should~ have included your original malleus patch, see: ./v.pl p verbose rotor/TEST2 asciilifeform_malleus_mikehearnificarum.vpatch
mod6: which btw, we need to update that build script.
mod6: must be the one he built with build-bitcoind-V99996.sh or whatever.
mod6: i typically only do `&', w/o nohup
mod6: naw, it was 2015. lucky.
mod6: did mod6 lose a whole year
mod6: ooh maybe the original rating date is preseved.
mod6: i thought it was last year
mod6: mircea_popescu: ya, i should just load up on tools and threads, etc. and just let it rip.
mod6: that's great actually. i should just set-it-and-forget-it.
mod6: i miss playing. i gotta get back in there one of these times.
mod6: i should break it up, and do them in chunks
mod6: i think ~normally~ 15 minutes is probably plenty. but for me, i wait a while before updating ratings, so trying to do a pile of them at once isn't a good idea.
mod6: anyway. no worries.
mod6: included a script too.
mod6: took me ~12 minutes and i went as fast as I could.