log☇︎
19500+ entries in 0.036s
mod6: this thing has a cool 0x00FF00 && 0x000000 website
mod6: trinque: fantastic. thanks.
mod6: trinque: just have to wait until next block before it shows up in the deedbot.org list?
mod6: asciilifeform: sounds good. thanks for doing that.
mod6: <+asciilifeform> mod6 et al: http://dpaste.com/1PHPHRE.txt << ok thanks, I can just point at the deedbot submission then.
mod6: I'm currently working on the SoBA to close out the month, would like to point at the vdiff.sh that creats w/o timestamps in the document. Only reason that I bring it up. Thanks for taking a look. Wasn't sure if I missed it somehow.
mod6: bah, well disregard the above -- as this came from my orc.sh script with escaped shell vars, but you get the point i think.
mod6: diff -uNr \$1 \$2 | awk 'm = /^(---|\+\+\+)/{s="sha512sum \"" \$2 "\" 2>/dev/null " | getline x; if (s) { split(x, a, " "); o = a[1]; } else {o = "false";} print \$1 " " \$2 " " o} !m { print \$0 }'
mod6: #!/bin/bash
mod6: so i see, obv., the one that was submitted with The Full Orchestra, but i don't see your updated one that looks like:
mod6 looks
mod6: Oh it was?!
mod6: asciilifeform: hey, qq: are you going to post the modified vdiff.sh (creation of vpatch w/o timestamps) to the ml, or will it be included with your next submission of the full working solution?
mod6: ascii_field: ok np, seems to be happy again
mod6: level3 has some weird shit going on
mod6: http://dpaste.com/2DSEFH7.txt
mod6: hm i dunno, maybe it'll come back
mod6: ascii_field: 195.211.154.159 << looks down
mod6: !up ascii_field
mod6: *shrug*
mod6: signon: Sun Aug 2 15:11:02 2015
mod6: lol, my thing stays connected pretty well i guess.
mod6 resolves
mod6: looks that way.
mod6: weird.
mod6: (13:04) [freenode] -assbot(~assbot@unaffiliated/kakobrekla/bot/assbot)- Insufficient rights, mod6, !up yourself on PM first.
mod6: hmm that's weird. what am i, stale?
mod6: !up ascii_field
mod6: !s banix
mod6: <+mircea_popescu> (03:51:56) >Mircea has managed 0.17 BTC worth of crafting! Congratulations! << enough to buy breakfast! << this :D
mod6: mircea_popescu: that's awesome
mod6: ;;calc 235*.17
mod6: ;;ticker
mod6: low was 0.00014430 on mar. 23rd according to btcalpha ☟︎
mod6: haha
mod6: http://log.bitcoin-assets.com/?date=25-05-2015#1144946 ☝︎☟︎
mod6: http://therealbitcoin.org/ml/btc-dev/2015-August/000158.html
mod6: heheh
mod6: everytime i see that stuff on the shelf, i think, "this shit is a metephor for the whole goddamn thing."
mod6: but it also makes this abortion: http://www.smuckers.com/products/peanut-butter/goober-pb-j/goober-grape-38
mod6: "food"
mod6: ahh yah, canola, saw fields upon fields of this driving through manatoba
mod6: heh 'rapeseed'
mod6: Ingrediant: SOYBEAN OIL
mod6: i can go look. this is 'vegetable oil'
mod6: but maybe im pierogie heathen
mod6: i got these ones from a lady from .ua at the farmers makert. instructions on the top said "don't cook in water", don't cook if frozen. so I let 'em thaw overnight. then just put 'em in a pan with a bit of cooking oil. simmered 'em until golden. tasted great to me!
mod6: alright, i'll just wing-it
mod6: I'm about to try to fry up some of these cheese & potato pierogies .. any tips ? just fry 'em until golden brown ?
mod6: ok, yah, works. just needed to do `gpg --verify <sigfile> <origfile>`
mod6: oh aight, lemme see here...
mod6: so if we do <patchname>.<wotGuy>.sig then will fail
mod6: these sigs that you posted won't verify out-of-the box, not that i've tried. but the detached sig must match the file name with the exception of the trailing .sig on the end.
mod6: oh i just realized something.
mod6: that way a person can find the tarballs, etc.
mod6: alright, i'll leave them off, and maybe just leave a linkback in the body to your message.
mod6: s/it'd/i'd/
mod6: asciilifeform: I see you attached the sigs for the vpatch files, and included the tarballs in your orchestra+breath-of-life (UPDATED) email. I think it'd like to attach the raw .vpatch files as well as the .sigs for completeness. Anything against this other than it's a bit redundant since you already posted the tarballs of the .vpatches?
mod6: <+asciilifeform> mod6: i recommend to follow the format nameofpatch.vpatch.mod6.sig << cool, sounds good.
mod6: <+asciilifeform> mod6: don't bother signing the tarballs, they are included for completeness. the thing to be signed is vpatches. << ok np.
mod6: <+asciilifeform> http://therealbitcoin.org/ml/btc-dev/2015-August/000156.html << cool! i'll try to get mine signed here soon. today or tomorrow.
mod6: no worries, thx!
mod6: let me know if you validate further, mechanically, whenever you get a chance.
mod6: yup, np.
mod6: SHA256 (rel2-pre-vpatches.tar.gz) = efee5d6f7a442748fb0326f0eb01ad69dc585e896ebadcaa6699af09b495618c
mod6: SHA256 (rel1-vpatches.tar.gz) = 98f234a7ce0210efcd0e841818479a8d7495bb1ef50b90280453d252efccdbb3
mod6: asciilifeform: here's the individual patches, archived for your review: http://thebitcoin.foundation/misc/rel1-vpatches.tar.gz && http://thebitcoin.foundation/misc/rel2-pre-vpatches.tar.gz
mod6: asciilifeform: i can put up the individual .vpatch files for you to review tomorrow.
mod6: ah
mod6: funkenstein_: 0.4.3?
mod6: closed @ 16`459 on friday.
mod6: still a ways to go there... or maybe a bet on QE4
mod6: the chick with 3 fingers thinks its a good idea. and gavin says "hey, you can't do that!" to the lion. the lion says, "we WILL do that."
mod6: the fox in the red says "here's where we're going to tie you to a chair and dunk you in the river."
mod6: ty
mod6: my rotor+TEST2 has fully sync'd on gentoo. (3rd full sync with -verifyall) ☟︎
mod6: Don't feel like it's a waste of time either to create your own method to generate these vpatches and see if we come out with the same resultant hash.
mod6: SHA256 (rel2.vpatch) = b951c4a56a362e8f936b65531298a2dad9cb456e3b15118f26ca9f61e5b9a97f
mod6: SHA256 (rel1.vpatch) = 717171ffffce57b7008968a4d8eb2a627f8fe45e4ed8eb15634fd1c1ddf868c5
mod6: Anyway, here are the hashes for the rel1.vpatch & rel2.vpatch
mod6: I dunno why it says error... links work for me.
mod6: mircea_popescu asciilifeform ben_vulpes trinque & all: For your review. http://thebitcoin.foundation/misc/orc.sh && http://thebitcoin.foundation/misc/rel1.vpatch && http://thebitcoin.foundation/misc/rel2.vpatch ☟︎
mod6: This script is huge, but does quite a bit too. I'll post it and the resulting rel1.vpatch and rel2.vpatch here in a bit.
mod6: for rel1 & rel2
mod6: now my sha256 manifests match from the original to the one-shot whole orchestra
mod6: ah, thx phf
mod6: oh the functionallity of "automatically pruning empty files" ?
mod6: yeah, just did. solves it.
mod6: dang, so close. i've basically got a rel1.vpatch and a rel2.vpatch all set -- but I'm seeing one strange thing... after doing the one-shot patching of either: rel1.vpatch leaves an empty 'makefile.linux-mingw' and 'qtui.h', while rel2.vpatch leaves an empty 'irc.h' and 'irc.cpp'.
mod6: Yes, Sir :]
mod6: now just gotta do it for rel2-pre and clean it up a bit and i think i'll have something for you guys to look at.
mod6: it's a one shot, straight to rel1 source.
mod6: oh this is pretty neat. so I got the mechanics tested & rebased for rel1 -- off of classic patches & genesis.vpatch to be sure. created a "rel1.vpatch" from that. then tested it, worked good on top of extracted genesis.vpatch. then did one of these numbers "cat genesis.vpatch >> rel1-fromair.vpatch ; cat rel1.vpatch >> rel1-fromair.vpatch ; patch -p1 < rel1-fromair.vpatch"
mod6: good deal. i'll see what I can do about the mechanical checking and rebasing maybe later tonight, or tomorrow for sure.
mod6: yup yup, i recall. just trying to make sure i'm on the right track so i don't waste everyones time :]
mod6: asciilifeform: ok, got it figured: check here please: http://thebitcoin.foundation/misc/rel1-test-20150822.patch && http://thebitcoin.foundation/misc/rel2-pre-test-20150822.patch
mod6: ok i think i see what I did wrong here... just a minute.
mod6: lemme blow these away
mod6: i did something wrong here.
mod6: the hashes don't match.