1 2016-08-22 02:03:53 0|BlueMatt|sipa: oops, sorry for the late response on the cmpctblock v2 bip, but I think I might've fucked you with the versioning scheme :/
2 2016-08-22 07:26:33 0|GitHub22|[13bitcoin] 15laanwj opened pull request #8558: Add copyright header to wallet_text_fixture.cpp (06master...062016_08_wallet_test_fixture_copyright) 02https://github.com/bitcoin/bitcoin/pull/8558
3 2016-08-22 08:01:00 0|GitHub30|13bitcoin/06master 14fa785d1 15MarcoFalke: Use __func__ to get function name for output printing
4 2016-08-22 08:01:00 0|GitHub30|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/2468292a0353...a55a018d5f2d
5 2016-08-22 08:01:01 0|GitHub30|13bitcoin/06master 14a55a018 15Wladimir J. van der Laan: Merge #8548: [wallet] Use __func__ to get function name for output printing...
6 2016-08-22 08:01:15 0|GitHub157|[13bitcoin] 15laanwj closed pull request #8376: [Wallet][Trivial] Fix exception message to reference actual thrower. (06master...062016-07-19-cwallet-sethmasterkey) 02https://github.com/bitcoin/bitcoin/pull/8376
7 2016-08-22 08:01:18 0|GitHub27|[13bitcoin] 15laanwj closed pull request #8548: [wallet] Use __func__ to get function name for output printing (06master...06Mf1608-walletFunc) 02https://github.com/bitcoin/bitcoin/pull/8548
8 2016-08-22 08:21:44 0|GitHub169|13bitcoin/06master 14faaec13 15MarcoFalke: [qa] Remove unused code
9 2016-08-22 08:21:44 0|GitHub169|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/a55a018d5f2d...760741a00833
10 2016-08-22 08:21:45 0|GitHub169|13bitcoin/06master 14760741a 15MarcoFalke: Merge #8551: [qa] Remove unused code...
11 2016-08-22 08:21:56 0|GitHub173|[13bitcoin] 15MarcoFalke closed pull request #8551: [qa] Remove unused code (06master...06Mf1608-qaUnused) 02https://github.com/bitcoin/bitcoin/pull/8551
12 2016-08-22 08:32:52 0|GitHub77|13bitcoin/06master 14653bb3d 15Wladimir J. van der Laan: Add copyright header to wallet_text_fixture.cpp...
13 2016-08-22 08:32:52 0|GitHub77|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/760741a00833...bb0f763a253f
14 2016-08-22 08:32:53 0|GitHub77|13bitcoin/06master 14bb0f763 15Wladimir J. van der Laan: Merge #8558: Add copyright header to wallet_text_fixture.cpp...
15 2016-08-22 08:33:02 0|GitHub185|[13bitcoin] 15laanwj closed pull request #8558: Add copyright header to wallet_text_fixture.cpp (06master...062016_08_wallet_test_fixture_copyright) 02https://github.com/bitcoin/bitcoin/pull/8558
16 2016-08-22 08:36:55 0|GitHub50|13bitcoin/06master 144207630 15Daniel Kraft: trivial: remove unused variable...
17 2016-08-22 08:36:55 0|GitHub50|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/bb0f763a253f...37e77c106cb5
18 2016-08-22 08:36:56 0|GitHub50|13bitcoin/06master 1437e77c1 15Wladimir J. van der Laan: Merge #8554: trivial: remove unused variable...
19 2016-08-22 08:37:10 0|GitHub62|[13bitcoin] 15laanwj closed pull request #8554: trivial: remove unused variable (06master...06remove-block-tmp) 02https://github.com/bitcoin/bitcoin/pull/8554
20 2016-08-22 08:49:54 0|xinxi|sipa: http://www.8btc.com/we-are-satoshi-provably-correct-bitcoin
21 2016-08-22 08:50:03 0|xinxi|I guess you will be interested.
22 2016-08-22 08:52:22 0|sipa|xinxi: I don't know chinese :)
23 2016-08-22 08:53:12 0|xinxi|It does not really matter as long as you can recognise your nice photo and the github url.
24 2016-08-22 08:53:40 0|sipa|haha
25 2016-08-22 08:54:27 0|xinxi|We may start to prove Bitcoin soon.
26 2016-08-22 08:54:42 0|sipa|good luck
27 2016-08-22 08:55:18 0|xinxi|yeah, it's not an easy project. We need some luck and your guys' help.
28 2016-08-22 10:00:28 0|sipa|wumpus: time to tag 0.13.0?
29 2016-08-22 10:28:13 0|wumpus|sipa: ACK
30 2016-08-22 10:29:11 0|wumpus|oh I missed the highlight here somehow: https://github.com/bitcoin/bitcoin/issues/8518
31 2016-08-22 10:31:18 0|sipa|i'd fix #8555 if it's obvious what the solution is
32 2016-08-22 10:31:28 0|sipa|but it's so minor that we could as well do it for 0.13.1
33 2016-08-22 10:34:54 0|btcdrak|wumpus: i found a blocker, really sorry...
34 2016-08-22 10:36:04 0|wumpus|* [new tag] v0.13.0 -> v0.13.0
35 2016-08-22 10:36:07 0|wumpus|btcdrak: oh no!
36 2016-08-22 10:36:38 0|btcdrak|hehe. was just joking
37 2016-08-22 11:28:41 0|btcdrak|finally! proof sipa is actually a machine!
38 2016-08-22 11:39:58 0|GitHub40|[13bitcoin] 15jonasschnelli opened pull request #8559: Fix maxuploadtarget recommended minimum calculation (06master...062016/08/max_ut) 02https://github.com/bitcoin/bitcoin/pull/8559
39 2016-08-22 11:48:10 0|wumpus|btcdrak: oh no, the machine conspiracy behind bitcoin is out in the open now
40 2016-08-22 11:53:12 0|sipa|you will be assimilated
41 2016-08-22 12:56:04 0|Thireus|Hi guys
42 2016-08-22 12:56:37 0|Thireus|Can someone please post the sha256sum and md5sum of v0.13.0.tar.gz?
43 2016-08-22 13:09:30 0|wumpus|Thireus: just the source tarball?
44 2016-08-22 13:09:37 0|wumpus|b89b2d68db7fee03cf1db6331386f1a56c2d759a31f745f0283858df6ebc986c src/bitcoin-0.13.0.tar.gz
45 2016-08-22 13:09:53 0|wumpus|that is "b89b2d68db7fee03cf1db6331386f1a56c2d759a31f745f0283858df6ebc986c"
46 2016-08-22 13:10:48 0|Thireus|the release
47 2016-08-22 13:11:11 0|Thireus|https://github.com/bitcoin/bitcoin/releases/tag/v0.13.0
48 2016-08-22 13:11:44 0|wumpus|strictly spoken there is no release yet just a tag
49 2016-08-22 13:12:00 0|Thireus|that one is the rc3
50 2016-08-22 13:12:35 0|Thireus|https://github.com/bitcoin/bitcoin/releases
51 2016-08-22 13:12:53 0|Thireus|I can see a release there
52 2016-08-22 13:13:05 0|Thireus|what's the difference?
53 2016-08-22 13:13:38 0|wumpus|that it wasn't built and checked yet
54 2016-08-22 13:14:00 0|Thireus|ok thanks
55 2016-08-22 13:14:03 0|Thireus|will wait then :)
56 2016-08-22 13:14:37 0|wumpus|you cn use rc3, by definition there have been no code changes since
57 2016-08-22 13:16:00 0|wumpus|just pushed gitian sigs for 0.13.0: https://github.com/bitcoin-core/gitian.sigs/blob/master/0.13.0-linux/laanwj/bitcoin-linux-0.13-build.assert
58 2016-08-22 13:16:42 0|Thireus|ah that's what I was looking for as well, thanks
59 2016-08-22 13:16:55 0|Thireus|I'll stick to the previous release for now
60 2016-08-22 13:17:10 0|Thireus|just wanted to make sure I had a non-tempered version of the 0.13.0
61 2016-08-22 13:17:24 0|Thireus|1cee144c1a359d0f202be401744f9be7
62 2016-08-22 13:17:24 0|Thireus|852581d21716b74e0539f7fd2f9c17f5506f1c21c5cec6642b0286823ba97193
63 2016-08-22 13:17:24 0|Thireus|md5sum v0.13.0.tar.gz:
64 2016-08-22 13:17:24 0|Thireus|sha256sum v0.13.0.tar.gz:
65 2016-08-22 13:17:24 0|Thireus|that's the hashes I've gt
66 2016-08-22 13:17:52 0|wumpus|how did you create it?
67 2016-08-22 13:17:59 0|Thireus|I downloaded it
68 2016-08-22 13:18:12 0|Thireus|https://github.com/bitcoin/bitcoin/releases
69 2016-08-22 13:18:12 0|Thireus|it's on the release page of the Bitcoin github
70 2016-08-22 13:18:13 0|wumpus|it's not available for download yet, it will be uploaded once three people have the same gitian output
71 2016-08-22 13:18:31 0|wumpus|that's just a tarball of the repository
72 2016-08-22 13:18:32 0|Thireus|3 hours ago
73 2016-08-22 13:18:32 0|Thireus|https://github.com/bitcoin/bitcoin/commit/a402396dce64c42ea73535b7dde4a9164d430438 https://github.com/bitcoin/bitcoin/archive/v0.13.0.zip https://github.com/bitcoin/bitcoin/archive/v0.13.0.tar.gz
74 2016-08-22 13:18:32 0|Thireus|https://github.com/bitcoin/bitcoin/releases/tag/v0.13.0https://github.com/bitcoin/bitcoin/releases/tag/v0.13.0ââ¬Â¦
75 2016-08-22 13:18:42 0|wumpus|as I said, there is no release yet
76 2016-08-22 13:18:52 0|Thireus|that's what I use when I compile the sources
77 2016-08-22 13:19:04 0|wumpus|you can download a dump of the repository for a certain tag from github, but that's not the same as a release
78 2016-08-22 13:19:12 0|wumpus|it's the same as you would get with 'git clone'
79 2016-08-22 13:19:33 0|Thireus|uhm
80 2016-08-22 13:19:51 0|Thireus|I don't know the release process
81 2016-08-22 13:20:05 0|Thireus|github ââ¬â> flagegd for release ââ¬â> ââ¬Â¦ ââ¬â> ?
82 2016-08-22 13:20:11 0|wumpus|https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md
83 2016-08-22 13:20:27 0|Thireus|thanks
84 2016-08-22 13:21:07 0|Thireus|I see, I was missing some extra steps
85 2016-08-22 13:21:19 0|Thireus|gitian especially
86 2016-08-22 13:21:49 0|wumpus|you can also build from a tag from git yourself, sure, but then it doesn't make sense to ask that the hash is here. You should check the signature on the tag "git tag -v v0.13.0".
87 2016-08-22 13:26:23 0|achow101|Anyone else having problems with gitian on Ubuntu 16.04
88 2016-08-22 13:35:22 0|jonasschnelli|achow101: I'm on Debian 7. Works wonderful with KvM
89 2016-08-22 13:39:07 0|achow101|how do I set it up using kvm? I'm using lxc right now
90 2016-08-22 13:39:43 0|jonasschnelli|Not sure how I did it...
91 2016-08-22 13:39:58 0|jonasschnelli|Did it aprox 1 year ago.
92 2016-08-22 13:41:05 0|achow101|time to hit up the gitian builder docs then
93 2016-08-22 13:41:44 0|wumpus|lxc is slightly more difficult to set up, as it requires some global configuration
94 2016-08-22 13:42:02 0|wumpus|kvm on the other hand doesn't usually work when nested in a VM
95 2016-08-22 13:42:36 0|MarcoFalke|achow101: The doc would be here: https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-descriptors/README.md
96 2016-08-22 13:42:57 0|jonasschnelli|Yes. I guess KVM requires to run the gitian host on a physical machine, although VMWare can emulate KVM in a VM.
97 2016-08-22 13:43:08 0|achow101|wumpus: lxc isn't working for me, and I am not using a vm as the host (thankfully)
98 2016-08-22 13:43:55 0|wumpus|jonasschnelli: right, there is some CPU bit, that if you VM environment supports it, and it is enabled, can allow for nested virtualization :)
99 2016-08-22 13:44:28 0|wumpus|but I'm not aware of anyone using it in that way, it seems awfully specific
100 2016-08-22 13:47:27 0|wumpus|Gavin had a very strange setup at some point where he built in vmware w/ Ubuntu VM directly. But the problem of using an 'alternative' setup is that it may have differences that result in different executables
101 2016-08-22 13:48:01 0|wumpus|(although this is mostly solved with the depends system, there is no reliance on any OS-shipped libraries)
102 2016-08-22 13:48:37 0|Lauda|I have the same problems as achow101 https://i.imgur.com/PIBLTPN.png
103 2016-08-22 13:48:43 0|Lauda|Inside a VM - Linux Mint 18
104 2016-08-22 13:49:39 0|wumpus|Lauda: maybe stupid suggestion: can you try running the command again? I have a similar problem which appears only the first time I run something with lxc after VM boot
105 2016-08-22 13:49:52 0|wumpus|the second and later times it just works (TM)
106 2016-08-22 13:50:38 0|wumpus|there's something weird with the LXC setup but I don't know enough about it to debug it
107 2016-08-22 13:52:13 0|wumpus|(it may be that some setup step has to be done in advance which is skipped by gitian, so a race condition happens)
108 2016-08-22 13:52:25 0|Lauda|It's actually a script from achow101, but following the gitian guide also resulted in the same problem (IIRC). Secondary run - http://i.imgur.com/c9CRLo3.png
109 2016-08-22 13:52:35 0|Lauda|Then it proceeds to provide the same errors for each build
110 2016-08-22 13:53:01 0|wumpus|the /dev/shm line is probably where you need to look for the error
111 2016-08-22 13:53:48 0|wumpus|this docker error looks similar https://github.com/docker/docker/issues/12912
112 2016-08-22 13:55:54 0|Lauda|There's nothing there besides a few pulse-shm files. Thanks for the link, I'll look into it
113 2016-08-22 14:04:48 0|sipa|bitcoin core 0.13 ARM signature validation speed on Nexus 5X: 1.03ms/txin
114 2016-08-22 14:05:22 0|instagibbs|havent built gitian in quite a while, what does "export SIGNER=" supposed to look like
115 2016-08-22 14:06:09 0|sipa|instagibbs: whatever you want to call youself
116 2016-08-22 14:06:23 0|wumpus|usually the first part of your email address, but something that can be passed to gpg to identify your key
117 2016-08-22 14:06:27 0|instagibbs|ok, something corresponding to your uid i assume
118 2016-08-22 14:06:34 0|wumpus|you can also use the gpg key-id
119 2016-08-22 14:06:37 0|instagibbs|wumpus, ok
120 2016-08-22 14:06:49 0|sipa|it's the directory name for your signatures under https://github.com/bitcoin-core/gitian.sigs/tree/master/0.13.0rc1-linux for example
121 2016-08-22 14:07:01 0|wumpus|yes, it's also used for the directory name
122 2016-08-22 14:15:50 0|achow101|how long should it take for gitian to check the a kvm image is running?
123 2016-08-22 14:27:38 0|jonasschnelli|http://bitcoin.stackexchange.com/questions/48171/bitcoine-core-wallet-is-not-stopping-synchronisation
124 2016-08-22 14:27:55 0|jonasschnelli|We should really improve sync information or add a SPV send-out mode in 0.14
125 2016-08-22 14:30:54 0|wumpus|yes
126 2016-08-22 14:40:30 0|GitHub93|13bitcoin/06master 14fab2e26 15crowning-: CDB: fix debug output...
127 2016-08-22 14:40:30 0|GitHub93|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/37e77c106cb5...41d8e78f94c5
128 2016-08-22 14:40:31 0|GitHub93|13bitcoin/06master 1441d8e78 15Wladimir J. van der Laan: Merge #8539: CDB: fix debug output...
129 2016-08-22 14:40:45 0|GitHub51|[13bitcoin] 15laanwj closed pull request #8539: CDB: fix debug output (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/8539
130 2016-08-22 14:55:18 0|achow101|for some reason my qemu vm for gitian won't start
131 2016-08-22 16:35:48 0|cfields_|gitian builders: v0.13.0 sigs are up
132 2016-08-22 16:39:54 0|MarcoFalke|pushed both
133 2016-08-22 16:47:24 0|cfields_|MarcoFalke: got it, thanks
134 2016-08-22 16:47:52 0|timothy|hi, when will you release the 0.13 tarballs?
135 2016-08-22 16:50:06 0|sipa|when we have enough gitian builds
136 2016-08-22 16:51:08 0|sipa|presumably in the next day or so
137 2016-08-22 18:02:30 0|michagogo|Looks like it's just one set of signeds short
138 2016-08-22 18:02:49 0|michagogo|(My set is building right now)
139 2016-08-22 18:16:26 0|michagogo|Apparently someone over at Debian made patches relating to GCC 6 and OpenSSL 1.1 -- has anyone here seen that and looked to see if it makes sense?
140 2016-08-22 18:16:46 0|michagogo|(I mean, someone who actually has the ability to evaluate that... unlike myself :-/ )
141 2016-08-22 18:20:28 0|michagogo|Never mind, I misread
142 2016-08-22 18:20:47 0|michagogo|Looks like both were fixed on our end -- it was just the bugs that were closed by the new uploads
143 2016-08-22 18:28:14 0|aj|michagogo: there were a couple of ssl patches due to EVP_CIPHER_CTX and EVP_MD_CTX and ECDSA_SIG becoming opaque that are still needed as of rc3, https://github.com/ajtowns/bitcoin-deb/blob/master/debian/patches/3001_openssl_1_1_fixes.patch (kinda ugly since what works with openssl 1.1 doesn't work with openssl 1.0.2...)
144 2016-08-22 18:29:24 0|michagogo|Ah.
145 2016-08-22 18:29:41 0|michagogo|Is that patch PR'd?
146 2016-08-22 18:30:27 0|michagogo|aj: ^
147 2016-08-22 18:30:36 0|aj|michagogo: no, it's not; feel free to open one
148 2016-08-22 18:33:20 0|michagogo|aj: I don't know enough about the code (or code in general) to feel comfortable with that
149 2016-08-22 18:33:33 0|michagogo|s/with/doing/
150 2016-08-22 18:34:09 0|michagogo|I mean, if it breaks earlier OpenSSL it probably needs some kind of configure-time check to activate or not activate the patch
151 2016-08-22 18:34:15 0|michagogo|(Or something)
152 2016-08-22 18:34:39 0|gmaxwell|perhaps we should drop the openssl comparison functions from the tests. :( it's not worth carrying around a bunch of openssl version ifdefs just for tests.
153 2016-08-22 18:35:10 0|gmaxwell|at least for libsecp256k1 we can make the openssl test in configure just not find 1.1
154 2016-08-22 18:35:56 0|sipa|we don't use the EVP_* stuff anymore in 0.13, right?
155 2016-08-22 18:36:44 0|gmaxwell|sipa: look at the patch.
156 2016-08-22 18:36:57 0|gmaxwell|Payment protocol.
157 2016-08-22 18:37:43 0|gmaxwell|sorry I didn't redflag this, I'd also thought we had eliminated all that openssl usage.
158 2016-08-22 18:37:55 0|sipa|oh, i didn't see there was a 'bitcoin' in that URL
159 2016-08-22 18:38:15 0|sipa|i thought you were talking about some generic openssl patches
160 2016-08-22 18:38:35 0|gmaxwell|sipa: no openssl 1.1 has ripped out a bunch of the leaky api.