1 2017-11-04T00:08:32  *** Cogito_Ergo_Sum has quit IRC
  2 2017-11-04T00:15:03  <achow101> why were there no commit messages in IRC?
  3 2017-11-04T00:19:23  <gmaxwell> they don't show up on other branches?
  4 2017-11-04T00:24:26  <sipa> i assume that's it
  5 2017-11-04T00:28:58  *** CubicEar_ has quit IRC
  6 2017-11-04T00:31:42  <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11604: [net] Remove ForNode/ForEachNode (master...2017-11-no-foreachnode) https://github.com/bitcoin/bitcoin/pull/11604
  7 2017-11-04T00:31:51  <bitcoin-git> [bitcoin] TheBlueMatt closed pull request #10697: Do not hold cs_vNodes when making ForEachNode Callbacks (master...2017-06-cnodestateaccessors-5) https://github.com/bitcoin/bitcoin/pull/10697
  8 2017-11-04T00:36:38  *** StopAndDecrypt has quit IRC
  9 2017-11-04T00:45:34  *** EL_CARTERO has quit IRC
 10 2017-11-04T00:45:51  *** StopAndDecrypt has joined #bitcoin-core-dev
 11 2017-11-04T00:45:51  *** LumberCartel has quit IRC
 12 2017-11-04T01:04:39  *** grio has joined #bitcoin-core-dev
 13 2017-11-04T01:16:30  *** vicenteH has quit IRC
 14 2017-11-04T01:21:09  *** vicenteH has joined #bitcoin-core-dev
 15 2017-11-04T01:23:29  *** jtimon has quit IRC
 16 2017-11-04T01:41:45  *** promag has joined #bitcoin-core-dev
 17 2017-11-04T01:44:38  *** quantbot has joined #bitcoin-core-dev
 18 2017-11-04T01:45:53  *** quantbot_ has joined #bitcoin-core-dev
 19 2017-11-04T01:45:53  *** quantbot has quit IRC
 20 2017-11-04T02:05:15  *** promag has quit IRC
 21 2017-11-04T02:08:54  *** twistedline has left #bitcoin-core-dev
 22 2017-11-04T02:09:04  *** d9b4bef9 has quit IRC
 23 2017-11-04T02:10:24  *** d9b4bef9 has joined #bitcoin-core-dev
 24 2017-11-04T02:21:00  *** ghost43 has quit IRC
 25 2017-11-04T02:21:52  *** ghost43 has joined #bitcoin-core-dev
 26 2017-11-04T02:27:16  *** cheese_ has quit IRC
 27 2017-11-04T03:00:51  *** xinxi has quit IRC
 28 2017-11-04T03:01:27  *** xinxi has joined #bitcoin-core-dev
 29 2017-11-04T03:04:37  *** LumberCartel has joined #bitcoin-core-dev
 30 2017-11-04T03:50:55  *** quantbot_ has quit IRC
 31 2017-11-04T04:02:11  *** quantbot has joined #bitcoin-core-dev
 32 2017-11-04T04:45:15  *** xinxi has quit IRC
 33 2017-11-04T04:45:48  *** xinxi has joined #bitcoin-core-dev
 34 2017-11-04T04:49:02  *** arubi has quit IRC
 35 2017-11-04T04:50:00  *** arubi has joined #bitcoin-core-dev
 36 2017-11-04T04:57:04  *** xinxi has quit IRC
 37 2017-11-04T04:57:39  *** xinxi has joined #bitcoin-core-dev
 38 2017-11-04T05:12:04  *** kkode has quit IRC
 39 2017-11-04T05:12:44  *** quantbot has quit IRC
 40 2017-11-04T05:18:06  <ossifrage> Should linearize-data.py still work? It fails sometime after 486000 with "Invalid magic: 00000000", from blk01005.dat (dated Sept 22, 2017)
 41 2017-11-04T05:19:01  <ossifrage> The resulting .dat file then fails to load with --loadblock
 42 2017-11-04T05:26:13  <gmaxwell> ossifrage: you need to go add segwit support to it, would be my guess.
 43 2017-11-04T05:34:34  *** murr4y has quit IRC
 44 2017-11-04T06:11:04  *** d9b4bef9 has quit IRC
 45 2017-11-04T06:12:11  *** d9b4bef9 has joined #bitcoin-core-dev
 46 2017-11-04T06:50:20  *** Lauda has quit IRC
 47 2017-11-04T06:50:51  *** Lauda has joined #bitcoin-core-dev
 48 2017-11-04T07:13:19  *** quantbot has joined #bitcoin-core-dev
 49 2017-11-04T07:17:35  *** quantbot has quit IRC
 50 2017-11-04T07:32:27  *** SopaXorzTaker has quit IRC
 51 2017-11-04T07:33:39  *** SopaXorzTaker has joined #bitcoin-core-dev
 52 2017-11-04T08:19:17  *** ula|2 has quit IRC
 53 2017-11-04T08:19:52  <wumpus>  * [new tag]         v0.15.1rc1 -> v0.15.1rc1
 54 2017-11-04T08:24:52  <meshcollider> \o/
 55 2017-11-04T08:26:22  *** SopaXorzTaker has quit IRC
 56 2017-11-04T08:26:26  <meshcollider> will start gitian building now then
 57 2017-11-04T08:26:59  *** SopaXorzTaker has joined #bitcoin-core-dev
 58 2017-11-04T08:28:40  *** justan0theruser has quit IRC
 59 2017-11-04T08:33:07  *** grio has quit IRC
 60 2017-11-04T08:41:20  *** ula has joined #bitcoin-core-dev
 61 2017-11-04T08:48:32  *** promag has joined #bitcoin-core-dev
 62 2017-11-04T08:51:29  *** fanquake has joined #bitcoin-core-dev
 63 2017-11-04T09:02:46  *** promag has quit IRC
 64 2017-11-04T10:09:18  *** btcdrak has quit IRC
 65 2017-11-04T10:10:37  <fanquake> I've PR some sigs if anyone wants to compare.
 66 2017-11-04T10:12:36  <meshcollider> linux looks good, still building windows and mac atm
 67 2017-11-04T10:15:51  *** NielsvG has quit IRC
 68 2017-11-04T10:16:26  *** jouke has quit IRC
 69 2017-11-04T10:21:11  *** NielsvG has joined #bitcoin-core-dev
 70 2017-11-04T10:21:13  *** NielsvG has joined #bitcoin-core-dev
 71 2017-11-04T10:58:32  *** cheese_ has joined #bitcoin-core-dev
 72 2017-11-04T11:05:01  *** murr4y has joined #bitcoin-core-dev
 73 2017-11-04T11:05:56  <Lauda> ping wumpus
 74 2017-11-04T11:23:42  *** laurentmt has joined #bitcoin-core-dev
 75 2017-11-04T11:54:30  *** xinxi has quit IRC
 76 2017-11-04T11:54:52  *** dermoth has quit IRC
 77 2017-11-04T11:55:04  *** xinxi has joined #bitcoin-core-dev
 78 2017-11-04T12:00:43  *** Provoostenator has joined #bitcoin-core-dev
 79 2017-11-04T12:02:30  *** quantbot has joined #bitcoin-core-dev
 80 2017-11-04T12:04:50  *** jtimon has joined #bitcoin-core-dev
 81 2017-11-04T12:07:36  *** dermoth has joined #bitcoin-core-dev
 82 2017-11-04T12:16:38  *** cheese_ has quit IRC
 83 2017-11-04T12:18:04  *** quantbot has quit IRC
 84 2017-11-04T12:18:40  *** quantbot has joined #bitcoin-core-dev
 85 2017-11-04T12:22:57  *** quantbot has quit IRC
 86 2017-11-04T12:34:22  <Provoostenator> Is v0.15.1 simply what was called v0.15.0.2 before? I.e. some tweaks to deal with the upcoming fork, but not full SegWit support?
 87 2017-11-04T12:35:00  <Provoostenator> And also, is it useful if I run Gitian on this?
 88 2017-11-04T12:37:10  *** joemphilips_ has joined #bitcoin-core-dev
 89 2017-11-04T12:42:10  <wxss> Provoostenator: to your first question, v0.15.1 (previously called v0.15.0.2) is the extra release to better deal with the 2X shitshow. Segwit support had to be delayed because of this to the next release, likely to be called v0.15.2
 90 2017-11-04T12:42:43  <Provoostenator> @wxss thanks
 91 2017-11-04T13:01:09  <bitcoin-git> [bitcoin] Sjors opened pull request #11605: [Qt] Enable RBF by default (master...rbf-default) https://github.com/bitcoin/bitcoin/pull/11605
 92 2017-11-04T13:07:36  <Provoostenator> ^ that was me
 93 2017-11-04T13:11:05  *** g_ has joined #bitcoin-core-dev
 94 2017-11-04T13:18:07  *** ekrion has joined #bitcoin-core-dev
 95 2017-11-04T13:27:28  *** voilk has joined #bitcoin-core-dev
 96 2017-11-04T13:34:49  *** warxhead has quit IRC
 97 2017-11-04T14:42:27  *** AaronvanW has joined #bitcoin-core-dev
 98 2017-11-04T14:51:44  *** mlz has quit IRC
 99 2017-11-04T14:53:40  <Provoostenator> I'm trying to make a Gitian build. Installing Virtual Box and Debian was easy, but this part of the instructions is confusing: https://github.com/bitcoin-core/docs/blob/master/gitian-building.md
100 2017-11-04T14:53:55  <Provoostenator> (VirtualBox running on OSX)
101 2017-11-04T14:54:03  <Provoostenator> bitcoin/contrib/gitian-build.sh --setup --lxc -b signer v0.15.1rc1
102 2017-11-04T14:54:22  <Provoostenator> (or with 0.15.1 instead of v0.15.1rc1)
103 2017-11-04T14:54:57  <MarcoFalke> What is the issue?
104 2017-11-04T14:55:16  *** mlz has joined #bitcoin-core-dev
105 2017-11-04T14:55:52  <Provoostenator> It starts with a bunch of errors:
106 2017-11-04T14:55:52  <Provoostenator> Cannot build for OSX, SDK does not exist. Will build for other OSes
107 2017-11-04T14:55:54  <Provoostenator> v-b
108 2017-11-04T14:55:54  <Provoostenator> Reading package lists... Done
109 2017-11-04T14:55:56  <Provoostenator> Building dependency tree
110 2017-11-04T14:55:56  <Provoostenator> Reading state information... Done
111 2017-11-04T14:55:58  <Provoostenator> E: Unable to locate package python-vm-builder
112 2017-11-04T14:55:58  <Provoostenator> fatal: destination path 'gitian.sigs' already exists and is not an empty directory.
113 2017-11-04T14:56:00  <Provoostenator> fatal: destination path 'bitcoin-detached-sigs' already exists and is not an empty directory.
114 2017-11-04T14:56:00  <Provoostenator> fatal: destination path 'gitian-builder' already exists and is not an empty directory.
115 2017-11-04T14:56:02  <Provoostenator> ~/gitian-builder ~ ~
116 2017-11-04T14:56:02  <Provoostenator> Then it seems to move along happily, e.g.:
117 2017-11-04T14:56:04  <Provoostenator> I: Configuring initramfs-tools...
118 2017-11-04T14:56:04  <Provoostenator> I: Configuring ureadahead...
119 2017-11-04T14:56:06  <Provoostenator> I: Base system installed successfully.
120 2017-11-04T14:56:06  <Provoostenator> 1+0 records in
121 2017-11-04T14:56:08  <Provoostenator> 1+0 records out
122 2017-11-04T14:56:08  <Provoostenator> 1048576 bytes (1.0 MB) copied, 0.00145623 s, 720 MB/s
123 2017-11-04T14:56:10  <Provoostenator> mke2fs 1.42.12 (29-Aug-2014)
124 2017-11-04T14:56:10  <Provoostenator> Discarding device blocks: done
125 2017-11-04T14:56:12  <Provoostenator> Creating filesystem with 2621440 4k blocks and 656640 inodes
126 2017-11-04T14:56:12  <Provoostenator> Filesystem UUID: 7b433e1a-b962-473d-8192-3c78d20ec64a
127 2017-11-04T14:56:14  <Provoostenator> Superblock backups stored on blocks:
128 2017-11-04T14:56:14  <Provoostenator> 	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
129 2017-11-04T14:56:16  <Provoostenator> Allocating group tables: done
130 2017-11-04T14:56:16  <Provoostenator> Writing inode tables: done
131 2017-11-04T14:56:18  <Provoostenator> Creating journal (32768 blocks): done
132 2017-11-04T14:56:18  <Provoostenator> Writing superblocks and filesystem accounting information: done
133 2017-11-04T14:56:20  <Provoostenator> And then it fails:
134 2017-11-04T14:56:20  <eck> plz
135 2017-11-04T14:56:20  <Provoostenator> ~ ~
136 2017-11-04T14:56:22  <eck> no flooding
137 2017-11-04T14:56:22  <Provoostenator> ~/bitcoin ~ ~
138 2017-11-04T14:56:22  <Provoostenator> error: pathspec 'v-b' did not match any file(s) known to git.
139 2017-11-04T14:56:23  <Apocalyptic> have you heard of pastebin ?
140 2017-11-04T14:56:24  <Provoostenator> Oops, I'll use a gist
141 2017-11-04T14:56:41  <MarcoFalke> You'd need to fetch the osx sdk somewhere
142 2017-11-04T14:56:41  <Provoostenator> My IRC client split the message up in 100 parts, that wasn't the plan.
143 2017-11-04T14:56:53  <eck> yes, that is how IRC works
144 2017-11-04T14:57:07  <MarcoFalke> I think they are hosted on some apple developer website
145 2017-11-04T14:57:24  <MarcoFalke> Also, random people might have uploaded them to GitHub somewhere
146 2017-11-04T14:57:46  <MarcoFalke> You can also skip the osx build for now
147 2017-11-04T14:57:54  <Provoostenator> I have an Apple developer account, so that should be doable. Do I need to get the old MaxOSX10.11 stuff?
148 2017-11-04T14:58:35  <Provoostenator> Skipping it is probably better for now, I'd like to see ifI can get the other builds to work.
149 2017-11-04T14:58:53  *** meshcollider has quit IRC
150 2017-11-04T15:02:03  <MarcoFalke> Refer to https://github.com/bitcoin/bitcoin/blob/master/doc/README_osx.md for instructions to download the apple sdk
151 2017-11-04T15:03:17  <Provoostenator> I've seen those instructions; they're not really clear, but I'll give it a shot.
152 2017-11-04T15:03:50  <Provoostenator> (I'll make some PR's to improve them once I manage to do a succesfull build)
153 2017-11-04T15:18:24  *** AaronvanW has quit IRC
154 2017-11-04T15:18:59  *** AaronvanW has joined #bitcoin-core-dev
155 2017-11-04T15:19:30  *** justanotheruser has joined #bitcoin-core-dev
156 2017-11-04T15:19:50  *** justanotheruser has joined #bitcoin-core-dev
157 2017-11-04T15:23:17  *** AaronvanW has quit IRC
158 2017-11-04T15:23:35  <achow101> Provoostenator: it should be 0.15.1rc1 not v0.15.1rc1
159 2017-11-04T15:26:02  <achow101> Provoostenator: there's no --lxc option
160 2017-11-04T15:26:15  <achow101> lxc is what it uses by default
161 2017-11-04T15:26:39  <Provoostenator> Ok and "signer" needs to be my email (for the PGP key)?
162 2017-11-04T15:26:48  <achow101> yes
163 2017-11-04T15:27:33  <achow101> does not necessarily need to be your email, could just be your username or some name that GPG recognizes
164 2017-11-04T15:28:10  <Provoostenator> Github username?
165 2017-11-04T15:28:15  <achow101> yeah
166 2017-11-04T15:29:28  <achow101> if that doesn't match your PGP key, you can use --detach-sign and sign it later. the signer name is used to organize the sigs into folders with each signer's name so having something like github username for that is better
167 2017-11-04T15:30:21  <Provoostenator> So I should either move my GPG key onto the VM, or just do the actual signing on my machine?
168 2017-11-04T15:31:05  <achow101> yes
169 2017-11-04T15:31:15  <achow101> I suggest signing on your machine
170 2017-11-04T15:33:54  <Provoostenator> debian@debian:~$ bitcoin/contrib/gitian-build.sh -b sjors 0.15.1rc1 --detached-sign
171 2017-11-04T15:33:55  <Provoostenator> lxcbr0: ERROR while getting interface flags: No such device
172 2017-11-04T15:33:56  <Provoostenator> SIOCSIFADDR: No such device
173 2017-11-04T15:34:09  <sipa> you don't have lxc
174 2017-11-04T15:34:54  <Provoostenator> I didn't see any obvious errors while doing this: https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-debian.md#setting-up-debian-for-gitian-building
175 2017-11-04T15:36:10  *** Chris_Stewart_5 has joined #bitcoin-core-dev
176 2017-11-04T15:47:24  *** cheese_ has joined #bitcoin-core-dev
177 2017-11-04T15:51:55  <Provoostenator> Switching bitcoin repo to master first did the trick. This might be related: https://github.com/bitcoin/bitcoin/pull/11391
178 2017-11-04T15:59:58  *** RoyceX has joined #bitcoin-core-dev
179 2017-11-04T16:02:47  *** cheese_ has quit IRC
180 2017-11-04T16:04:45  *** joemphilips_ has quit IRC
181 2017-11-04T16:05:35  *** dabura667 has joined #bitcoin-core-dev
182 2017-11-04T16:06:20  *** fanquake has quit IRC
183 2017-11-04T16:15:16  *** jouke has joined #bitcoin-core-dev
184 2017-11-04T16:15:35  *** RoyceX has quit IRC
185 2017-11-04T16:17:59  *** cheese_ has joined #bitcoin-core-dev
186 2017-11-04T16:19:27  *** neha has joined #bitcoin-core-dev
187 2017-11-04T16:23:32  *** cheese_ has quit IRC
188 2017-11-04T16:27:01  *** AaronvanW has joined #bitcoin-core-dev
189 2017-11-04T16:30:03  *** cheese_ has joined #bitcoin-core-dev
190 2017-11-04T16:30:40  *** dabura667 has quit IRC
191 2017-11-04T16:33:42  *** donaloconnor has joined #bitcoin-core-dev
192 2017-11-04T16:33:47  *** jouke_ has joined #bitcoin-core-dev
193 2017-11-04T16:34:02  <donaloconnor> Can anyone point to me where in the code bitcoin core checks if the block hash is valid? - I can see it checks POW in CheckBlockHeader
194 2017-11-04T16:34:21  <sipa> what does that mean?
195 2017-11-04T16:34:22  <donaloconnor> (FYI - I'm learning the protocol and stepping through the code)
196 2017-11-04T16:34:33  <sipa> as in, what do you mean by valid?
197 2017-11-04T16:35:02  *** quantbot has joined #bitcoin-core-dev
198 2017-11-04T16:35:03  <donaloconnor> the hash the miners generate for a block
199 2017-11-04T16:35:29  <sipa> which validity rule, i mean? difficulty, pow, merkle root commitment, ...?
200 2017-11-04T16:37:48  <sipa> and i can be a bit pedantic: the hash is computed - it's not that miners "claim" it has a certain hash; it's just how we identify blocks
201 2017-11-04T16:37:57  <sipa> by definition the hash itself is always valid
202 2017-11-04T16:38:07  *** cheese_ has quit IRC
203 2017-11-04T16:38:13  <sipa> of course, there are many rules that the block has to satisfy
204 2017-11-04T16:38:32  <donaloconnor> I guess it's pow? - I'm not entirely sure... apologies I'm learning. Miners generate the block hash to find one that satisfies the difficulty. I mean, where does bitcoin core check that this hash is actually valid (ie: hashing the block again results int he same hash)
205 2017-11-04T16:38:49  <sipa> it does not verify that anywhere
206 2017-11-04T16:38:55  <sipa> nobody claims a block has a certain hash
207 2017-11-04T16:39:16  <sipa> the block itself is propagated
208 2017-11-04T16:39:28  <sipa> and to be valid, its hash has to satisfy PoW
209 2017-11-04T16:39:47  <sipa> (but that's only one out of dozens of validity criteria)
210 2017-11-04T16:42:00  *** kkode has joined #bitcoin-core-dev
211 2017-11-04T16:44:49  <donaloconnor> my understanding was miners modified parts of the coinbase text + nonce in order to find something that will result in a hash that satisfies pow/difficulty (blocks start with 	0000000000000000003) now. I guess i'm asking, what's stopping someone generating a hash that begins with enough zeros that isn't actually the hash of the block header?
212 2017-11-04T16:45:01  <donaloconnor> I guess i'm missing something here, sorry if I'm sounding silly ;)
213 2017-11-04T16:45:14  <sipa> well then the block will be invalid
214 2017-11-04T16:45:27  <donaloconnor> well that's what I mean... where does it check that
215 2017-11-04T16:45:34  <sipa> perhaps we're arguing semantics
216 2017-11-04T16:45:58  <sipa> but there is no need to check whether the block matches its claimed hash - nobody ever claims it has a particular hash
217 2017-11-04T16:46:07  <sipa> the hash is computed from the block
218 2017-11-04T16:46:26  <sipa> the rule is _for a block to be valid_ that its hash is below the target implied by the difficulty
219 2017-11-04T16:46:38  <donaloconnor> maybe. I'm looking at ProcessNewBlock and trying to find out where it validates that the hash is infact a valid hash of the block contents.
220 2017-11-04T16:46:38  <sipa> and you've already found where that is checked
221 2017-11-04T16:46:48  <aj> donaloconnor: nodes don't communicate the hashes directly, the communicate the headers (and blocks) and then work out what the hash is
222 2017-11-04T16:46:52  <sipa> the hash is always the hash of the block contents
223 2017-11-04T16:46:56  <donaloconnor> ahhh
224 2017-11-04T16:46:57  <sipa> it is defined as such
225 2017-11-04T16:47:00  <donaloconnor> maybe that's it
226 2017-11-04T16:47:02  <donaloconnor> sorry
227 2017-11-04T16:47:18  <donaloconnor> now I understand...
228 2017-11-04T16:48:06  <donaloconnor> uint256 hash = block.GetHash(); << this is calculated by the nodes and not transmitted over the wire
229 2017-11-04T16:49:55  <sipa> exactly
230 2017-11-04T16:50:19  <donaloconnor> sipa/aj - thanks for the information.
231 2017-11-04T16:59:37  *** fobban has joined #bitcoin-core-dev
232 2017-11-04T17:03:28  <fobban> I'm running (or trying to run) bitcoin-core on arch linux but ever since v0.15 I get a CPU hardware error after a few minutes which causes the computer to reboot. I redownloaded the blockchain but a few seconds after it was complete I got the error again.
233 2017-11-04T17:03:50  <sipa> sounds like your CPU is overheating
234 2017-11-04T17:03:57  <fobban> I've got a i7-6700k. Never got these hardware errors before and I only get them once I start bitcoin core again
235 2017-11-04T17:04:24  <sipa> bitcoin core tends to stress CPUs far more than usual desktop software
236 2017-11-04T17:06:48  <fobban> ok, let me monitor the temp. I don't think it has to do with that though cause the fans don't really spin up more than usual, but hang on, will probably time out soon :P
237 2017-11-04T17:07:05  *** kkode has quit IRC
238 2017-11-04T17:09:11  <fobban> is v0.15 much harder on the cpu than 0.14 was?
239 2017-11-04T17:13:47  <sipa> yes, it needs to wait much less on memory
240 2017-11-04T17:14:29  *** spudowiar has joined #bitcoin-core-dev
241 2017-11-04T17:16:12  <fobban> I see now that I didn't get the crash when the blockchain was complete, I managed to download 91% before it crashed. But temp is steady between 23-30C on all cores.
242 2017-11-04T17:17:02  <donaloconnor> could be PSU not providing enough power for CPU
243 2017-11-04T17:18:41  *** Chris_Stewart_5 has quit IRC
244 2017-11-04T17:22:29  <fobban> Hm, might be temp after all, started to spike to 75C now o_O
245 2017-11-04T17:24:23  <donaloconnor> maybe, though 75 is not uncommon under high load
246 2017-11-04T17:31:30  *** PaulCapestany has quit IRC
247 2017-11-04T17:33:24  *** PaulCape_ has joined #bitcoin-core-dev
248 2017-11-04T17:35:04  *** aqquadro has joined #bitcoin-core-dev
249 2017-11-04T17:35:04  *** aqquadro has joined #bitcoin-core-dev
250 2017-11-04T17:40:43  *** dabura667 has joined #bitcoin-core-dev
251 2017-11-04T17:43:55  *** AaronvanW has quit IRC
252 2017-11-04T17:47:12  <Provoostenator> Gitian has been diligently working for the past few hours... Is there any way to spot check if the work in progress is correct?
253 2017-11-04T17:48:18  *** PaulCape_ has quit IRC
254 2017-11-04T17:49:18  *** spudowiar has left #bitcoin-core-dev
255 2017-11-04T17:50:03  *** PaulCapestany has joined #bitcoin-core-dev
256 2017-11-04T17:54:25  *** donaloconnor has quit IRC
257 2017-11-04T17:57:57  *** LumberCartel has quit IRC
258 2017-11-04T18:01:23  *** xinxi has quit IRC
259 2017-11-04T18:01:57  *** xinxi has joined #bitcoin-core-dev
260 2017-11-04T18:02:22  *** dabura667 has quit IRC
261 2017-11-04T18:07:44  <jouke> w/win 14
262 2017-11-04T18:08:49  <Provoostenator> To answer my own q: once all linux versions finish building, it spits out a summary with hashes. You can compare that with e.g. gitian.sigs/0.15.1rc1-linux/laanwj/bitcoin-linux-0.15-build.assert
263 2017-11-04T18:09:29  <Provoostenator> Hopefully this isn't a problem:
264 2017-11-04T18:09:29  <Provoostenator> ./bin/gsign:52:in `<main>': invalid option: --detach-sign (OptionParser::InvalidOption)
265 2017-11-04T18:10:02  *** Chris_Stewart_5 has joined #bitcoin-core-dev
266 2017-11-04T18:10:48  *** Deacyde has quit IRC
267 2017-11-04T18:15:09  *** AaronvanW has joined #bitcoin-core-dev
268 2017-11-04T18:24:49  *** AaronvanW has quit IRC
269 2017-11-04T18:25:28  *** AaronvanW has joined #bitcoin-core-dev
270 2017-11-04T18:27:07  *** dabura667 has joined #bitcoin-core-dev
271 2017-11-04T18:32:32  *** AaronvanW has quit IRC
272 2017-11-04T18:33:01  *** AaronvanW has joined #bitcoin-core-dev
273 2017-11-04T18:33:10  *** LumberCartel has joined #bitcoin-core-dev
274 2017-11-04T18:38:14  *** grio has joined #bitcoin-core-dev
275 2017-11-04T18:55:05  *** dabura667 has quit IRC
276 2017-11-04T18:56:57  *** LumberCartel has quit IRC
277 2017-11-04T18:58:02  *** dabura667 has joined #bitcoin-core-dev
278 2017-11-04T19:00:40  *** LumberCartel has joined #bitcoin-core-dev
279 2017-11-04T19:02:18  *** dabura667 has quit IRC
280 2017-11-04T19:03:35  *** meshcollider has joined #bitcoin-core-dev
281 2017-11-04T19:09:52  *** LumberCartel has quit IRC
282 2017-11-04T19:09:59  *** uneeb has joined #bitcoin-core-dev
283 2017-11-04T19:11:39  <meshcollider> Provoostenator: you can also look at the build logs as it's building, to see how it's going
284 2017-11-04T19:12:00  <meshcollider> And check for errors
285 2017-11-04T19:16:05  *** uneeb has quit IRC
286 2017-11-04T19:22:38  <Provoostenator> @meshcollider those are fun to watch. When I run ./bin/gverify, I assume it checks both the signatures of the other signers as well as that they have the same hashes in their assert files?
287 2017-11-04T19:30:44  <meshcollider> Provoostenator: hmm I don't think it checks the hashes, just checks the signatures are valid
288 2017-11-04T19:31:34  *** jtimon has quit IRC
289 2017-11-04T19:31:53  <Provoostenator> So how do I check that my hashes match what others found? I compared a few manually and they match.
290 2017-11-04T19:34:35  *** LumberCartel has joined #bitcoin-core-dev
291 2017-11-04T19:38:41  *** laurentmt has quit IRC
292 2017-11-04T19:38:45  <bitcoin-git> [bitcoin] Sjors opened pull request #11607: Add Gitian PGP key: Sjors (master...gitian-sjors) https://github.com/bitcoin/bitcoin/pull/11607
293 2017-11-04T19:40:47  *** AaronvanW has quit IRC
294 2017-11-04T19:41:01  *** Chris_Stewart_5 has quit IRC
295 2017-11-04T19:51:36  *** cheese_ has joined #bitcoin-core-dev
296 2017-11-04T19:53:57  *** LumberCartel has quit IRC
297 2017-11-04T19:58:22  *** zshlyk has quit IRC
298 2017-11-04T19:59:40  *** cheese_ has quit IRC
299 2017-11-04T19:59:41  *** zshlyk has joined #bitcoin-core-dev
300 2017-11-04T20:00:24  *** aqquadro has quit IRC
301 2017-11-04T20:22:49  <ossifrage> :-( ./libtool: line 1720: 10983 Segmentation fault      (core dumped) /usr/bin/gcc-ar cru .libs/libsecp256k1.a src/libsecp256k1_la-secp256k1.o
302 2017-11-04T20:28:58  *** Evel-Knievel has quit IRC
303 2017-11-04T20:34:02  *** jtimon has joined #bitcoin-core-dev
304 2017-11-04T20:35:45  *** owowo has quit IRC
305 2017-11-04T20:40:38  *** owowo has joined #bitcoin-core-dev
306 2017-11-04T20:40:38  *** owowo has joined #bitcoin-core-dev
307 2017-11-04T20:58:11  *** Chris_Stewart_5 has joined #bitcoin-core-dev
308 2017-11-04T20:58:23  *** AaronvanW has joined #bitcoin-core-dev
309 2017-11-04T21:01:34  *** Aaronvan_ has joined #bitcoin-core-dev
310 2017-11-04T21:03:01  *** AaronvanW has quit IRC
311 2017-11-04T21:09:36  *** LumberCartel has joined #bitcoin-core-dev
312 2017-11-04T21:10:53  *** Provoostenator has quit IRC
313 2017-11-04T21:11:34  *** Aaronvan_ has quit IRC
314 2017-11-04T21:12:12  *** AaronvanW has joined #bitcoin-core-dev
315 2017-11-04T21:13:23  *** AaronvanW has quit IRC
316 2017-11-04T21:13:40  *** AaronvanW has joined #bitcoin-core-dev
317 2017-11-04T21:16:21  <gmaxwell> ossifrage: hurray compiler bug.. or cpu overheating
318 2017-11-04T21:18:10  <ossifrage> I was trying (again) to get a flto compile with the current tree. I'm assuming it is a toolchain bug
319 2017-11-04T21:18:35  <ossifrage> ./libtool: line 1720:  1040 Segmentation fault      (core dumped) /usr/bin/gcc-ranlib .libs/libsecp256k1.a
320 2017-11-04T21:19:05  <gmaxwell> which gcc version
321 2017-11-04T21:20:23  <ossifrage> gcc is 7.2.1, gcc-ar is 2.27-24
322 2017-11-04T21:21:50  <ossifrage> Initially I was getting "plugin needed to handle lto object" from /usr/bin/ranlib, so I switched to gcc-{ranlib,ar,nm}
323 2017-11-04T21:23:36  <gmaxwell> fwiw, there should be no LTO benefit from libsecp256k1 itself, it's a single .c file.  (the modules are all in seperate header files, specifically so it gets all the inlining gains possible, without using LTO)
324 2017-11-04T21:25:42  <ossifrage> gmaxwell, I'm compiling the entire tree with lto, it just happened to go boom on libsecp256k1
325 2017-11-04T21:28:16  <gmaxwell> ossifrage: in any case, I'm jealous, not that often that you get to report a GCC bug. :P
326 2017-11-04T21:31:40  *** shesek has quit IRC
327 2017-11-04T21:38:44  <esotericnonsense> ossifrage: ryzen gcc segfault bug ?
328 2017-11-04T21:42:44  <ossifrage> esotericnonsense, this is an old xeon (with ecc) and it is repeatable (so not some thermal silliness)
329 2017-11-04T21:42:53  <esotericnonsense> ah
330 2017-11-04T21:43:22  *** meshcollider has quit IRC
331 2017-11-04T21:46:37  *** Chris_Stewart_5 has quit IRC
332 2017-11-04T21:48:26  *** promag has joined #bitcoin-core-dev
333 2017-11-04T21:49:05  *** fobban has quit IRC
334 2017-11-04T21:59:28  *** LumberCartel has quit IRC
335 2017-11-04T22:19:18  *** spinza has quit IRC
336 2017-11-04T22:25:45  *** Chris_Stewart_5 has joined #bitcoin-core-dev
337 2017-11-04T22:32:58  *** spinza has joined #bitcoin-core-dev
338 2017-11-04T22:43:22  <cfields> gitian builders: v0.15.1rc1 codesigs are _finally_ pushed
339 2017-11-04T22:44:29  *** AaronvanW has quit IRC
340 2017-11-04T22:44:44  *** promag has quit IRC
341 2017-11-04T22:45:07  *** AaronvanW has joined #bitcoin-core-dev
342 2017-11-04T22:47:13  *** sava_ has joined #bitcoin-core-dev
343 2017-11-04T22:47:16  <sava_> hello,
344 2017-11-04T22:47:38  <sava_> can anyone tell me command to create new wallet address in linux please
345 2017-11-04T22:48:45  <sipa> sava_: #bitcoin
346 2017-11-04T22:49:23  *** AaronvanW has quit IRC
347 2017-11-04T22:51:02  <sava_> its BTCGPU for bitcoin gold i installed
348 2017-11-04T22:52:10  *** Emcy_ has joined #bitcoin-core-dev
349 2017-11-04T22:53:00  <sipa> sava_: not here, #bitcoin
350 2017-11-04T22:53:23  <sipa> oh, it's for an altcoin - in that case, no idea
351 2017-11-04T22:53:27  *** Emcy has quit IRC
352 2017-11-04T22:53:50  <sava_> cheers
353 2017-11-04T22:53:53  *** sava_ has quit IRC
354 2017-11-04T22:55:05  <windsok> #bitcoin-forks
355 2017-11-04T23:01:06  *** AaronvanW has joined #bitcoin-core-dev
356 2017-11-04T23:11:12  *** AaronvanW has quit IRC
357 2017-11-04T23:24:13  *** AaronvanW has joined #bitcoin-core-dev
358 2017-11-04T23:26:36  *** AaronvanW has quit IRC
359 2017-11-04T23:42:35  *** Chris_Stewart_5 has quit IRC
360 2017-11-04T23:44:28  *** kkode has joined #bitcoin-core-dev
361 2017-11-04T23:48:39  *** fanquake has joined #bitcoin-core-dev
362 2017-11-04T23:48:49  *** dermoth has quit IRC
363 2017-11-04T23:49:15  *** dermoth has joined #bitcoin-core-dev
364 2017-11-04T23:49:17  *** kkode has quit IRC
365 2017-11-04T23:49:23  <fanquake> cfields lagging as per usual :p
366 2017-11-04T23:52:18  <fanquake> Have pushed some signed sigs up.