--- Log opened Thu Feb 06 00:00:31 2020
03:04 -!- Danielle52Beahan [~Danielle5@ns334669.ip-5-196-64.eu] has joined #bitcoin-builds
03:47 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 252 seconds]
04:32 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #bitcoin-builds
04:37 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Ping timeout: 260 seconds]
04:38 < MarcoFalke> wumpus: Want to chat about when to remove the link to the i686 binaries on the website? I think it should be done one release prior to when we stop building the binaries. This way we have an easy way to backtrack in case a ton of i686 users pop up.
04:38 < MarcoFalke> I think you did it that way for the win32 binaries
04:42 -!- Danielle52Beahan [~Danielle5@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 272 seconds]
04:57 < wumpus> MarcoFalke: I think that makes sense, hadn't thought of it like that yet
04:58 < MarcoFalke> I am asking because I have assinged https://github.com/bitcoin/bitcoin/issues/17504 to 0.20.0
04:58 < MarcoFalke> Happy to postpone it to 0.21.0, though
04:59 < wumpus> so then the question is to stop building them for 0.20 or 0.21, given how little people seem to care about it, stopping building them for 0.20 would probably be okay
04:59 < wumpus> in which case removing the link as soon as possible is better
05:00 < MarcoFalke> Yeah, that was my thinking
05:00 < MarcoFalke> I can raise it in the meeting today as a short topic to see if anyone disagrees
05:16 < wumpus> sure, we could do that
05:40 < dongcarl> fanquake: It seems we've found a few reproducibility problems with NSIS then... Here's a recent fix that might help us: https://sourceforge.net/p/nsis/bugs/1230/
05:40 < dongcarl> fanquake: bumping the nsis right now to see if there's any effect.
05:41 < dongcarl> probably good to upstream and to ditch libfaketime once and for all
05:41 < dongcarl> (not that this is a faketime issue, but just if we encounter any time issues in the future)
05:43 < fanquake> dongcarl: interesting!
05:45 < wumpus> so even with faketime, NSIS doesn't generate deterministic output every time? interesting
05:46 < wumpus> having random memory end up in the executable is terrible
05:47 < wumpus> we had a problem like that with ld on windows as well once
06:04 < MarcoFalke> dongcarl: The nsis build problems are known: https://github.com/bitcoin/bitcoin/pull/13827
06:08 < fanquake> MarcoFalke: looks like that was missing the time linker flags at least?
06:08 < dongcarl> MarcoFalke: That looks a little different, no? I think fanquake and I are seeing a diff in the installer exes, while #13827 is seeing a diff w/re the makensis binary?
06:08 < MarcoFalke> oh
06:09 < MarcoFalke> right dongcarl
06:15 -!- jonatack [~jon@109.232.227.133] has joined #bitcoin-builds
07:13 -!- wumpus [~ircclient@pdpc/supporter/professional/wumpus] has quit [Ping timeout: 245 seconds]
07:19 -!- wumpus [~ircclient@pdpc/supporter/professional/wumpus] has joined #bitcoin-builds
08:22 -!- jonatack [~jon@109.232.227.133] has quit [Ping timeout: 260 seconds]
09:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
09:33 -!- kcalvinalvin [~kcalvinal@ec2-52-79-199-97.ap-northeast-2.compute.amazonaws.com] has quit [Ping timeout: 265 seconds]
09:34 -!- kcalvinalvin [~kcalvinal@ec2-52-79-199-97.ap-northeast-2.compute.amazonaws.com] has joined #bitcoin-builds
14:54 < fanquake> dongcarl: any luck with the newer nsis?
14:54 < fanquake> I see GREAT-CORE-UPDATE-MERGE updates
16:58 < fanquake> I did 2 more builds using nsis 3.05, and that doesn't seem to have fixed the installer issues, will investigate further.
22:35 -!- midnightmagic is now known as midnight
22:40 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
22:53 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-builds
--- Log closed Fri Feb 07 00:00:32 2020