--- Log opened Wed Apr 14 00:00:25 2021
02:55 < emzy> I get a "build of /gnu/store/vhphki5sg9xkdhh2pbc8gi6vhpfzryf0-gnutls-3.6.12.drv failed" "FAIL: status-request-revoked" "cert_verify_callback:263: certificate verify status doesn't match: 100402 != 22FAIL status-request-revoked (exit status: 1)"
03:01 < emzy> I see it is a known issue. https://issues.guix.gnu.org/44559
03:25 -!- Jamarcus16Jaskol [~Jamarcus1@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-builds
03:37 < hebasto> it seems ubuntu hirsute could become a main dev environment -- guix and clang-12 (for TSan) packages in repo :)
03:46 < wumpus> it's nice that pip has a hash-checking mode, i wasn't aware-not sure how it deals with indirect deps?
03:46 < wumpus> oh "Hashes are required for all dependencies. An error results if there is a dependency that is not spelled out and hashed in the requirements file." good
03:48 < wumpus> hebasto: i generally try to stick to LTS releases but must agree that sounds attractive
06:29 -!- belcher_ is now known as belcher
06:52 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
06:56 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 268 seconds]
07:26 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds]
07:38 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
07:44 -!- Jamarcus16Jaskol [~Jamarcus1@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 260 seconds]
09:21 < dongcarl> emzy: Yup... That's unfortunate... Let me post a snippet of my upcoming README for you
09:24 < sipa> emzy: if you are fine with just trusting that one package, it's possible to enable substitutes just for that
09:24 < sipa> other solutions are significantly more complicated for now
09:25 < dongcarl> emzy: https://gist.github.com/dongcarl/7a4a9339a7877cff17b29689e9c22c53
09:26 < emzy> tnx. I will try the hard workaround first :)
09:27 < sipa> dongcarl: i'm somewhat surprised guix doesn't globally mock time
09:27 < dongcarl> emzy: You are brave!
09:27 < sipa> as that seems like a common source of variation in builds
09:28 < dongcarl> sipa: It has been discussed... The time namespace is only for monotonic time: https://issues.guix.gnu.org/44559#3
09:28 < gribble> https://github.com/bitcoin/bitcoin/issues/3 | Encrypt wallet · Issue #3 · bitcoin/bitcoin · GitHub
09:28 < dongcarl> If faketime were applied across the board... I'm guessing there would be many more failures haha
09:29 < dongcarl> Hopefully someday the kernel hackers will decide to flesh out the time namespace, but I would guess it'd be quite an undertaking
09:42 < sipa> oh, powerpc64 build also succeeded on aarch64 host
09:42 < sipa> *powerpc64le
09:46 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
10:02 < wumpus> dongcarl: given the amount of optimization applied to the time system call (including kernel dso and a single page mapped into every process), i expect time namespacing to be quite involved
10:02 < emzy> dongcarl: tnx. Looks good on first try. "PASS: status-request-revoked"
10:03 < sipa> wumpus, dongcarl: it seems more reasonable to just have standard guix infrastructure to make libfaketime usage easy for derivations that need, i guess
10:03 < sipa> but the hard part will be identifying which ones need it :p
10:04 < wumpus> yes, at least as long as downstream build systems aren't adopted yet to not needing it
10:05 < wumpus> like not embedding build timestamps in the first place
10:06 < sipa> right
10:25 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
10:31 < dongcarl> emzy: Oh yay!
10:36 < dongcarl> sipa: I think that's why Guix has all the package transformation options/procedures, so that you can programmatically change build recipes at a finer level (perhaps you want faketime for only one test and don't want it for another). The main problem here is the GnuTLS is special in the dependency tree and isn't affected by the transformation
10:36 < dongcarl> options, but I would hope that this is resolvable sometime in the future...
12:32 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
12:34 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
14:15 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
14:17 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
14:17 < jonatack> jonasschnelli: bitcoinbuilds seems to be down..."Warning:  SQLite3::query(): Unable to prepare statement: 5, database is locked in /home/jonasschnelli/discopop/www/index.php on line 143"
14:17 < jonatack> and "Fatal error: Uncaught Error: Call to a member function fetchArray() on boolean in /home/jonasschnelli/discopop/www/index.php:428 Stack trace: #0 {main} thrown in /home/jonasschnelli/discopop/www/index.php on line 428"
14:17 < gribble> https://github.com/bitcoin/bitcoin/issues/0 | HTTP Error 404: Not Found
14:52 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has quit [Remote host closed the connection]
14:53 -!- jonasschnelli [~jonasschn@static.239.36.216.95.clients.your-server.de] has joined #bitcoin-builds
14:53 -!- jonasschnelli [~jonasschn@static.239.36.216.95.clients.your-server.de] has quit [Changing host]
14:53 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #bitcoin-builds
14:53 < jonasschnelli> jonatack: thanks... looking into it
18:16 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
18:17 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 252 seconds]
18:18 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
18:22 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 252 seconds]
18:23 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 252 seconds]
18:38 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
20:26 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds]
20:40 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-builds
--- Log closed Thu Apr 15 00:00:26 2021