--- Log opened Wed Jun 30 00:00:52 2021
01:15 -!- Guest84 [~Guest84@2001:e68:543f:e602:f903:5558:4bc1:61da] has joined #bitcoin-core-builds
01:16 -!- Guest84 [~Guest84@2001:e68:543f:e602:f903:5558:4bc1:61da] has quit [Client Quit]
08:36 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
08:40 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
10:20 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
10:22 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
11:12 -!- belcher_ is now known as belcher
15:08 -!- robertspigler [~robertspi@2001:470:69fc:105::2d53] has quit [Write error: Connection reset by peer]
15:09 -!- robertspigler [~robertspi@2001:470:69fc:105::2d53] has joined #bitcoin-core-builds
15:56 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 265 seconds]
16:47 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
17:21 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
17:24 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds]
20:21 -!- jtrag [~jtrag@c-71-207-125-151.hsd1.pa.comcast.net] has quit [Read error: Connection reset by peer]
21:00 -!- achow101 [~achow101@user/achow101] has quit [Quit: Bye]
21:00 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-builds
21:34 < hebasto> is gitian is supposed to be completely retired by 22.0 branch-off? If so, going to close #22281, #22287, #22305, #22318, #22321 in favor of #22365; if not, what is the plan?
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22281 | build: Avoid @GLIBC_2.29 libm symbols when --enable-glibc-back-compat by hebasto · Pull Request #22281 · bitcoin/bitcoin · GitHub
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22287 | build: Avoid fcntl64@GLIBC_2.28 symbol when --enable-glibc-back-compat by hebasto · Pull Request #22287 · bitcoin/bitcoin · GitHub
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22305 | An error has occurred and has been logged. Please contact this bot's administrator for more information.
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22318 | build: Avoid @GLIBC_2.25 symbols for compatibility by hebasto · Pull Request #22318 · bitcoin/bitcoin · GitHub
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22321 | build: Avoid qt-specific @GLIBC_2.28 symbols for compatibility by hebasto · Pull Request #22321 · bitcoin/bitcoin · GitHub
21:34 < gribble> https://github.com/bitcoin/bitcoin/issues/22365 | guix: Avoid relying on newer symbols by rebasing our cross toolchains on older glibcs by dongcarl · Pull Request #22365 · bitcoin/bitcoin · GitHub
21:35 < fanquake> hebasto: I've been thinking about that a bit, also why I hadn't bothered to  review any of those PRs yet
21:38 < hebasto> fanquake: as some of those fixes are not covered by `--enable-glibc-back-compat` and touch depends, I think we should not allow two different release build paths co-exist, and gitian must be retired
21:41 < sipa> i would assume gitian is being kept around so we don't run into problems if we at the last minute determine guix builds aren't feasible
21:41 < sipa> but i don't thinn the plan is to have gitian release binaried for 22.0 and up
21:42 < hebasto> keeping gitian around require aforementioned individual symbols fixups
21:45 < hebasto> fanquake: thanks for finding the root of the boost process problem and the detailed explanation - https://github.com/bitcoin/bitcoin/pull/22348#issuecomment-871061160
--- Log closed Thu Jul 01 00:00:53 2021