--- Log opened Sat Jun 26 00:00:49 2021
01:57 -!- belcher_ is now known as belcher
03:51 < hebasto> we made three releases (0.19, 0.20, 0.21) against glibc 2.27 from bionic distro -- everything was flawless, right?
03:51 < hebasto> so, my vote is for guix builds against glibc 2.24
03:53 < hebasto> tested https://github.com/hebasto/bitcoin/commits/dongcarl-glibc-210626 which is modified to drop glibc 2.17
04:03 < hebasto> ^ bitcoin-qt binaries are not built...
05:58 < hebasto> dongcarl: your branch does not build bitcoin-qt as well
10:50 -!- Guest42 [~Guest42@205.254.183.45] has joined #bitcoin-core-builds
10:52 < Guest42> Do we use Cirrus primarily for building? or are there any other popular options too?
10:52 < sipa> cirrus is CI
10:52 < sipa> you can run tests locally too of course
10:52 < Guest42> I was thinking to pick up https://github.com/bitcoin/bitcoin/issues/22206
10:54 < Guest42> the op mentioned that Cirrus even has a pip_cache key, so we are thinking to cache the libraries only for the CI or for every build never the less
10:55 < sipa> this isn't really an issue for actual builds, as those just use your own systems' libraries
10:55 < sipa> it's possibly an issue for gitian/guix builds, but those aren't something we do all the time for which time matters that much
10:56 < sipa> it's just in CI where doing those builds over and over again is a meaningful waste of time
10:57 < sipa> Guest42: the context is that in CI, every build happens in a fresh environment, which doesn't have the previously built libraries in it
10:57 < sipa> if you'd just run two builds in the same environment, this wouldn't be a problem - but the point of CI is that it's reproducible
10:58 < Guest42> Ah, I see, that makes much more sense now
10:58 < Guest42> thank you
11:37 < Guest42> Would trying to achieve this using Docker Images be a good start?
11:38 < sipa> to reproduce it, you mean?
11:40 -!- Guest4240 [~Guest42@205.254.183.171] has joined #bitcoin-core-builds
11:42 -!- Guest42 [~Guest42@205.254.183.45] has quit [Ping timeout: 246 seconds]
11:42 -!- Guest4240 is now known as Guest42
11:54 < Guest42> What it says at https://cirrus-ci.org/examples/#python for caching in Python Docker Images, applies for CI builds executed in a disposable container/disposable virtual machine as well?
11:54 < sipa> we're not using python docker images for our builds, as far as i know
11:57 < Guest42> Would trying to set one up be recommended? or will it be too deviating from the original path
11:58 < sipa> my guess is no, there are good reasons for why the current setup is as it is
11:59 < sipa> but it's probably better to ask on the issue, as not everyone involved is in IRC at this very moment
12:00 < Guest42> I get it, thank you so much
12:00 < Guest42> :)
12:05 -!- Guest42 [~Guest42@205.254.183.171] has quit [Quit: Client closed]
12:36 -!- Guest42 [~Guest42@205.254.183.171] has joined #bitcoin-core-builds
12:36 -!- Guest42 [~Guest42@205.254.183.171] has quit [Client Quit]
12:50 -!- Guest42 [~Guest42@205.254.183.171] has joined #bitcoin-core-builds
12:50 -!- Guest42 [~Guest42@205.254.183.171] has quit [Client Quit]
17:20 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
17:24 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 244 seconds]
--- Log closed Sun Jun 27 00:00:49 2021