19700+ entries in 0.04s
mod6: asciilifeform: your step "2)", do you mean to indicate reference [1] instead of "also [3]" which is the email to chicken?
mod6: <+asciilifeform> mod6, ben_vulpes, mircea_popescu, et al: << thanks ascii, will take a look.
mod6: did you add that patch to your currently running node on aws?
mod6: <+thestringpuller> the intent is to jettison the entire pool? (hopefully I'm reading the patch correctly). mod6 informed me of the boost datastructure idiocy << wait, wat?!
mod6: orchestra/rel2-pre.patch v. orchestra/test-v054-patches/rel2-pre-test.patch
mod6: orchestra/rel1.patch v. orchestra/test-v0531-patches/rel1-test.patch
mod6: Anyone who wants to please be a second pair of eyes here: run the script and then compare the scripts version to ascii's version:
mod6: So I've basically been able to reproduce both of your rel1.patch & rel2-pre.patch -- and I went through your patch with my script's created patch side by side by hand and verified the sha512s
mod6: asciilifeform: I have successfully reproduced the rel1.patch on my own now with the same matching antecedent/new hashes. I have script that reproduces this all the way up through v0.5.3.1 -- will continue on and do the same for up through v0.5.4 before let everyone see. But, so far, so good.
mod6: <+asciilifeform> mod6: what i have in mind is that this ends up being a box where you can drop in a sig (l1 !) and, optionally, one or more patches << yeah, this is good
mod6: asciilifeform: yeah, one email is ok by me. just was curious what you had in mind.
mod6: now, I need to just validate these hashes.
mod6: asciilifeform: ok cool! rel1.patch and rel2-pre.patch do apply cleanly to all of the existing patches
mod6: Sounds like from your email, that's pretty much the plan...
mod6: asciilifeform: Are you planning on posting each patch (that we've since included in rel1, rel2) in a separate email to the list with a detached sig and included sha512?
☟︎ mod6: Meanwhile, now I'm gonna see if I can figure out this new versioning email. The hard part is going to be having to verify everything posted, and re-writing all of our documentation.
mod6: So, if anyone wants to try out these automated cucumber tests on v0.5.4-TEST2 w/rotor ; I have some recipes that work on: ubuntu 10.04, deb6/7/8 and gentoo. Just send me a PM and I'll work with you on it.
mod6: <+shinohai> ;;later tell mod6 the real cumber^ << ahhaha
mod6: well... heh. I thought i'd get the chance to dive into your new email asciilifeform. But, guess it'll have to be tomorrow.
mod6: <+gernika> mod6: bastard blocks for roughly 10 hours now. Perhaps I corrupted my db? << hmm. not sure? are you getting errors as opposed to just bastard blocks? maybe post last 250 lines of your debug.log and we can have a look.
mod6: if start to see repeating errors in debug.log let us know.
mod6: ok, good deal. just let it do its thing.
mod6: do you have the maxint_locks_corrected patch applied?
mod6: oh i just deleted a ')', im screwed.
mod6: Oh, i didn't notice you could actually edit the examples. neat.
mod6: And it looks like you can take notes or something
mod6: Well, unless you count submitting the answers to the exercises.
mod6: cool. glad she tested it for us.
mod6: thank your ex-gf for me ;)
mod6: 'tis one of the reasons i enjoyed camping in the west so much, back east the mosquitoes try to carry you away.
mod6: where i live these things are not just a nuisance like in .ar, but ubiquitous
mod6: <+asciilifeform> ben_vulpes ? mod6 ? any of you went home with mosquito bite ? << heheh. i might have gotten a bite or two. i paid them back ~10x iirc.
mod6: oh ok will look thx.
mod6: comment out: "BR2_ARCH_IS_64=y" ? and set "BR2_i386=y" +
mod6: ascii_field: for people who'd like to build rotor w/stator or rotor w/TEST2 on i386/i686, is there anything special that they would need to do to this file? rotor_buildroot_dot_config
mod6: i'll post the diff so you can take a peek when you have a chance ascii_field
mod6: that kinda 25 <=> 12 happens a bunch
mod6: + 40259e: 48 81 ff 50 12 ac 00 cmp $0xac1250,%rdi
mod6: - 40259e: 48 81 ff 50 25 ac 00 cmp $0xac2550,%rdi
mod6: ok, yeah offsets, not opcodes:
mod6: <+ascii_field> and srsly do i have to do everything myself << i might not be viewing the differences correctly .. so what I said above might not be correct.
mod6: seems to be some opcode diffs, i.e. deb 0x25 always is changed out for gentoo 0x12 ...
mod6: hey, if i build rotor-TEST2 on say gentoo, and someone else builds the same whole thing on debian, we get the same number of output bytes in the bin, but the checksums are different, seem to be some offset differences.
mod6: I'm going to be afk for the rest of the night, but I can perhaps talk about it with you tomorrow.
mod6: Meanwhile, I can offer you a script that I use to patch up through maxint_locks_corrected from v0.5.3.1 -- it's not a guide, but if you read the steps, it's what needs to happen and in what order. The new (forthcoming) guide will be based on these steps:
http://dpaste.com/0YVSD6Q.txt mod6: hanbot: yeah, the guide needs to be updated. It's on the to-do list, just had my hands full lately. I can help you get patched up from v0.5.3.1 if you like. We can work on that this week.
mod6: im building on ubuntu 14.04 atm
mod6: <+ben_vulpes> after much derping, i have a rotor-built stator bitcoind << heeey! neat. :]
mod6: asciilifeform: im with you there.
mod6: oh. ok. you want to us to try it on the new thing they're working on, or exisitng, or both and compare?
mod6: busybox? any specific version?
mod6: awe shoot, realized i gotta wait until later tonight for ubuntu 14.04 test. my bad.
mod6: i guess i could try now on 14.04 LTS
mod6: i built on ubuntu 10.04, as well as deb6 and gentoo/hardened/nomultilib/libc
mod6: great work shinohai
mod6: shinohai: you built successfully with rotor-TEST2.sh on deb 8 right?
mod6: asciilifeform: any idea on funkenstein_'s error? maybe no build-essentials?
mod6: funkenstein_: ok this is a new one for me. what are the detalis: debian 8, x86-64... ok. is this with the rotor/stator hand build from ascii's guide with tea? or my thing I just posted a bit a go rotor-TEST2.sh?
mod6: yea, i think this all is about to get easier.
mod6: <+asciilifeform> ditto curl
mod6: (14:54) <+asciilifeform> btw rsync should be abolished when we mod the thing to stop pulling from the net
mod6: buildroot uses it to pull stuff it needs.
mod6: All: If you are going to build the rotor-TEST2.sh on debian be advised that you may need the following installed: build-essential curl unzip python bc rsync
mod6: kakobrekla: it needs a bit of cleanup before we're through
mod6: last reminder to all who are following along: TEST2 is patched up through maxint_locks_corrected
mod6: thanks asciilifeform
mod6: someone can also not run this as a script and just run these commands one line at a time if they please.
mod6: main major requirement x86-64
mod6: i have a script for you to look over, review, read, and try out if you like:
mod6: so now it extracts and it's just bitcoin/src
mod6: remember when jurov was mad at me because i put everything underneath of v0_5_3_1/ instead of just being what it was.
mod6: its just the way that jurov demands that it works.
mod6: asciilifeform: only main change I had to make other than pulling down the TEST2 bundle itself was to add this: sed -i 's/bitcoin\/bitcoin\/src/bitcoin\/src/' rotor.sh
mod6: ;;later tell pete_dushenski I have a script for you to try on Debian 7 to build TEST2 with rotor. You might need to install a few minor pre-reqs. I can hold your hand if required for that part. Let me know when you have some time.