mod6: if some vagina on the train told me to "watch my man spreding, i'd be like. ``fuck off, dickhead''" it's the only reasonable response you hvae left any more.

mod6: but yeah, i just `mkdir -p ~/.seals ~/.wot` and dropped the sigs into ~/.seals and the pub keys in ~/.wot and off it went.

mod6: this should do the trick: `LC_ALL=C ./bitcoind -myip=127.0.0.1 -addnode=195.211.154.159 &` ☟︎

mod6: yup, that's required on every system that i've encountered when built with the `rotor'.

mod6: ok, yah, works. just needed to do `gpg --verify <sigfile> <origfile>`

mod6: closed @ 16`459 on friday.

mod6: <+mircea_popescu> yeah, mod you have teh honor. << thanks. I've confirmed that what I get from genesis.vpatch out of thin air is the same manifest as `bitcoin-0.5.3-no-crud.sha256.manifest`.

mod6: just ran the `patch -p1 < genesis.vpatch` in an empty dir, and then volla, bitcoin source exists

mod6: yup, ok. and when I have my own genesis.vdiff, should compare with `diff -u` to the one you posted in your original email? or compare with vdiff?

mod6: I can say that your change to vdiff.sh `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 }'` certainly removes the timestamps from the output hashes.

mod6: <+asciilifeform> because afaik no one has yet done this. << I have 2x completed full sync with -verifyall. And I have further attemps #3 & #4 >300`000 blocks atm. ☟︎

mod6: <+hanbot> re ml: where are sha256sums for, eg, http://therealbitcoin.org/ml/btc-dev/2015-February/000040.html (patch)? << Hi, in the case of that patch email, the SHA1 sum is embedded in the file name. For example: asciilifeform_dnsseed_snipsnip_192f7bc7c14c1d31c7b417c9cd77be51c4d255f2.patch -- if you were to download this patch, you could then run `sha1sum asciilifeform_dnsseed_snipsnip_192f7bc7c14c1d31c7b417c9cd77be51c4d255f2.patch` and it sh

mod6: <+jurov> mod6 decrypt on *clearsigned* file << this indeed works. created file A.txt. copied A.txt to B.txt and subtracted some lines. created a unified diff of both. clearsigned the diff -- which is mutilated for escaped hyphens. upon `gpg --decrypt` of the clearsigned output patch file, i get the same hash as the pre-clearsigned hash file.

mod6: ascii_field: so does `gpg --decrypt` work for that as danielpbarron & jurov said?

mod6: please ensure that you are running x86_64 by doing `uname -a`

mod6: and there are 75`000 people and 50 submissions per day?

mod6: Thanks all for working lastnight to get the db locks issue resolved! I've got a new bitcoin-v0_5_4-TEST2 bundle created. Patch added was `asciilifeform_maxint_locks_corrected.patch'. Applies cleanly. All automated tests passed.

mod6: tell pete_dushenski <+punkman> do you have realpath? << Now that you have `realpath` installed, I'd try rebuilding the entire thing again. Thanks for testing!

mod6: ;;later tell pete_dushenski <+punkman> do you have realpath? << Now that you have `realpath` installed, I'd try rebuilding the entire thing again. Thanks for testing!