--- Log opened Tue Nov 02 00:00:21 2021
04:58 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Remote host closed the connection]
04:58 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has joined #bitcoin-core-builds
05:07 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Remote host closed the connection]
05:08 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has joined #bitcoin-core-builds
05:22 -!- laanwj [~laanwj@user/laanwj] has joined #bitcoin-core-builds
06:03 < josibake> what is the rational for pinning to a specific guix commit in `./contrib/guix/guix-build`? i can see in this commit it was updated to `aa34d4d28dfe25ba47d5800d05000fb7221788c0`: https://github.com/bitcoin/bitcoin/commit/201c5e4aec5210b258644ff96379cda0ca7273ab#diff-80d3f0ccda6db0d10dd0f660162c5039e30ed0095e78aed712a0f28dadbd9fc4
06:05 < sipa> josibake: otherwise presumably the build isn't deterministic
06:09 < josibake> sipa: interesting. i need to read up more on time-machine. the reason i ask is i just installed guix on my machine using the shell script (to get the latest version) and then tried to do a build and it failed with `guix time-machine: error: execl: No such file or directory`. i was able to fix it by running `guix describe` and then using the commit hash from there in the build script and now everything seems to be working
06:11 < josibake> so if im understanding this, regardless of which guix version i have installed, the build script is using a specific version for reproducibility, which will likely break from time to time as the pinned version diverges from my locally installed version?
06:12 < sipa> dongcarl may know more about that
06:13 < sipa> but you see why the pinning is necessary?
06:15 < dongcarl> josibake: Unfortunately I haven't run into that one before, but you should not need to change the commit hash for things to build...
06:17 < josibake> sipa: reading the documentation on time-machine and yes, this makes sense now
06:17 < dongcarl> josibake: If you change it back and do a build and it still fails, feel free to send over logs and I can take a look!
06:25 < josibake> dongcarl: initially, i installed guix using `sudo apt` and everything was fine, so i dont think it's a huge problem. i then purged and installed from the shell script, which installed the latest version of guix, and that's when i got the error. got it working now, but ill go back later and try to reproduce it 
07:28 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds
10:16 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
10:27 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds
11:06 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
11:40 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds
13:45 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
13:46 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
15:50 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 264 seconds]
--- Log closed Wed Nov 03 00:00:22 2021