17000+ entries in 0.029s
mod6: oops, copied too much there.
mod6: 565faf3ef371f5e2178ae30c45b08b93415eeb92263486e68f2ac2e8f4c7900056e628804bf5c0707a90be946e0aeaebfcd0a391aab40de2e5d56e6bcbdccb1e db.cpp
mod6: Thanks Sir. Much appreciated.# sha512sum db.cpp
mod6: Thanks Sir. Much appreciated.
mod6: TomServo's issues have me a bit curious there.
mod6: mircea_popescu: hey, just because im curious -- let me know if you get past 252`450 -- or if you'd rather, check and see if you have the most recent db.cpp
mod6: shinohai: that *is* weird.
mod6: hanbot: did you get it to work too?
mod6: btw, did it ever build ok for you after the 'bc' issue?
mod6: you think i should copy it somewhere in the v99996 build script before i jump onto other things? i'd rather just let sleeping dogs lie there, just because very soon we're gonna ditch it anyway.
mod6: mircea_popescu: no specific reason, we just leave it in place after compilation. moving to trinque's setup resolves this.
mod6: two weeks kinda sounds like it might be a lot, but you know how this stuff goes ;)
mod6: which would allow us some full testing time - at the end of which, we sign patches and call it a release.
mod6: I feel like, if you and I put some serious effort with help from #b-a, for like 2 weeks, we'd really be somewhere by the end of february.
mod6: <+trinque> I will probably be out all day tomorrow, but the next day or sometime next week will work for me. << no rush here. i'd like to dig into this sometime next week.
mod6: <+trinque>
http://log.bitcoin-assets.com//?date=24-01-2016#1384068 << I designed the makefiles to take a BUILDER variable, of which there is currently only rotor. ... << for now, as far as I'm concerned, this is totally ok. we'll have to worry about other *nix's after we perfect getting linux x86-64 done with a CD to boot also.
☝︎ mod6: <+trinque>
http://log.bitcoin-assets.com//?date=29-01-2016#1389272 << there's some tweaking I'd like to do, would be happy to have your thoughts on the thing when you're able if you see other improvements << yeah, please, if you have the time, i'd really like to work with you to help us not only get the makefiles updated with the latest V and other things, but to also figure out all of this stuff.
☝︎ mod6: I feel good about the work that you all put in this month. Thanks to everyone who helped the republic be successful this month.
mod6: Look at how much stuff we accomplished in January!
mod6: so stragicially, we're moving in the correct direction there.
mod6: i do think, as a republic, we're laying the groundwork for that at some point to be a possibility.
mod6: this to me always seems like a shaky idea -- ONLY even a possibility if we get all the compiler garbage fixed so that it produces (bitwise) the ~exact~ same binary every single time.
mod6: And hopefully, this will end some of our tooling issues for a while, and we can focus on the large engineering issues at hand.
mod6: As soon as we have our new build process in place, and it's sane, and "Works" and "fits in head" and all that, then we'll release.
mod6: which, I aim to work on tonight :]
mod6: that will be my main goal as soon as the SoBA for january is complete.
mod6: trinque did us all a huge favor, but we need to perfect the thing and make it a "no brainer"
mod6: Yup. It's complex. We've come a long way.
mod6: if someone says "hey fuck these ``Classic and XT clowns, I want REAL BITCOIN'', then we need to ensure that they can build that.
mod6: what good is fixing the mempool or other things if they can't build it and use it today?
mod6: But we can't work on that, until we have something that people can use today.
mod6: Then we'll be ready to take on the more challenging parts this year -- i.e. the mempool etc.
mod6: However, the process to build said binary is quite arduous and we need to perfect that part.
mod6: Yeah, the good news is: We have a statically linked bitcoind that has come quite a long way from where we started. Infact, the original version flat out will not work any longer -- ala TomServo's issue.
mod6: my goal is that someone who doesn't really know much -- but at least enough to install Linux can build this with a "single button push"
mod6: the entire build process is incredibly complex and we need to desperately reduce that compelxity as much as we can.
☟︎ mod6: if hanbot and Mr. P. can get through it ok, then we'll deedbot it -- not that I feel good about it - I don't. The thing isn't what we really want... it's just what we have, for now. :/
mod6: ok sweet. that's a good thing.
mod6: There are steps that I can let you know about to walk you through setting this up and logging your every move so we can all discover what it is that isn't working on your end. Because I'd bet dollars to donuts that for somereason you are ending up with a super downlevel version of db.cpp -- which is why you're getting stuck on 252`450
mod6: But we should attempt to get to the bottom of this as soon as possible.
mod6: Please, let's work together to discover what that might be. I'm worried that either V is failing on your side for some reason (it seems to not be pressing out the tree correctly) -- maybe you tried to build over an old build space, or who knows.
mod6: TomServo: ok, something very bad (tm) is happening on your end.
mod6: for sure let me know if there are other ones that you wanna know about :]
mod6: if you have .bitcoin/bitcoin.conf -- then you shouldn't need to use the flag: -conf
☟︎ mod6: if you want to connect to just a single node instead of many, use: -connect (instead of -addnode)
mod6: if you want to send btc and not get malleated, you may use: -lows
mod6: if you want to verify all signatures in a block; use -verifyall
mod6: if so you need to use -datadir=
mod6: But it totally depends. It depends on if you have ~/.bitcoin available for your blockchain repo, or if its in a different place.
mod6: <+hanbot>
http://log.bitcoin-assets.com/?date=29-01-2016#1389355 << if this isn't already a standard example, anyone feel like talking me through this option jungle? (starting v99996 for the first time) << so i think all that is really required here is `LC_ALL=C ./bitcoind -myip=A.B.C.D -addnode=W.X.Y.Z &`
☝︎ mod6: so yeah, after the first, will be a main focus there -- all are encouraged to help me get to this goal.
mod6: no exceptions to this.
mod6: it doesn't scale obviously for everyone to have these issues. for my own sanity, we need to make it so that a guy just basically does one thing and then it builds.
☟︎ mod6: obviously this is not how we want things to be -- will be the main focus to be to get rid of the build script we're using today and move to a version of trinque's makefiles.
mod6: <+mircea_popescu> ftr mod6 : i ended up with two rotor.sh scripts, one under rotor the other under rotor/test2 << yeah, if all goes well, you should ~only~ need to just execute the build script -- if you have to execute either of the rotor.sh scripts, then something went wrong.
☟︎ mod6: what's the cannonical makeclean, rm -rf * in /rotor ? << yeah, i would just blowaway the entire 'rotor' directory along with all the V stuff. the stuff that I would save is just the .wot dir, the keys contained therein, and of course, your ~/.gnupg stuff (ofc. have backups etc (this is for everyone who blew their keys away once)) : then totally restart the entire script.
mod6: <+mircea_popescu> You must install 'bc' on your build machine << ah, ok.
mod6: <+pete_dushenski> mod6: 99996k built and running. back to scarfing blocks. should be synced early next week. << ok awesome, glad you got it working
mod6: ok lemme try to answer some questions here...
mod6: thanks for testing that out.
mod6: pete_dushenski: ya, as soon as we get a couple of people confirming that v99996 builds for them correctly, we'll throw it into deedbot, but thanks!
mod6: so if i use -setvernum=99997 it'll show up in the log but not getinfo?
mod6: yup, thanks for your patience and willingness to work on this.
mod6: in here if nothing else.
mod6: this is of value since I really haven't played with this on my own. perhaps log your results and post.
mod6: yeah, i dont know. i'd try building with the new v99996 script, and then see what happens.
mod6: but this needs to be investigated for sure. or maybe asciilifeform has some example we can follow?
mod6: Now, with mine bitcoind, mine just comes up without setting any flags at all as 99999. so maybe try without any commandline flags first.
mod6: pete_dushenski: ok good q. shinohai had some issues with trying to set the value via the command line too - i haven't even tested this yet.
mod6: just want to make sure you're not stuck.
mod6: hanbot: alrighty, thanks. sometimes if I don't hear anything, i just assume the worst. heheh.
mod6: this thing doesn't play nice trying to run it more than one time with old artifacts laying around.
mod6: if you tried to build with this script, and something went wrong, which im pretty sure that it did, you need to blow everythign away (aside from your .wot dir and your keyring of course - have back ups! /me looks at people who blew away their keys) and start over.
mod6: hanbot: still having some probs?
mod6: <+mircea_popescu> ah nm, it was the x86 flag << yeah.
mod6: !up ascii_butugychag
mod6: # Required Public Keys to add to your PGP Keyring. These are used to verify V, rotor, buildroot, and trinque's patch:
mod6: # Required Public Keys to add to your PGP Keyring. This are used to verify V, rotor, buildroot, and trinque's patch:
mod6: mircea_popescu: ah, ok will fix.
mod6: as soon as i get through the end of this month, a renewed emphasis will be put on ditching this script, and getting to a finished place with trinque's makefiles that'll hopefully be easier to understand.
☟︎☟︎ mod6: I'll change the comment, standby.
mod6: to verify V, trinque's special patch, buildroot, and other stuff.