--- Log opened Thu Aug 05 00:00:29 2021
00:24 -!- copumpkin [~woohoo@user/copumpkin] has quit [Ping timeout: 272 seconds]
00:38 < laanwj> harding: maybe, but there's a lot of overhead there, doing it like this would mean every gitian signer has to sign every binary saperately
00:39 < laanwj> i use an external signer module myself where i have to push a button for every signature, so really prefer the single file approach
00:42 < laanwj> dongcarl: agree
00:52 < laanwj> and grouping the SHA256SUMS allows attesting to files (such as the -debug- files-, other source/intermediate files) that are not uploaded, but if someone wants to generate them they can compare the hash
01:02 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-builds
01:05 -!- belcher_ is now known as belcher
01:28 < laanwj> certainly there is some elegance to gpg-signing per file but just not sure it's a good match to our flow
01:31 -!- copumpkin [~woohoo@user/copumpkin] has joined #bitcoin-core-builds
04:27 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity]
05:24 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-builds
05:52 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
05:56 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
07:07 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
07:19 < jonatack> question, now that the 22.0rc2 binary is released, any point in still doing guix build+signing for it? the previous two times for rc1 took ~20 hours, so I'd prefer to not needlessly block the computer that long :)
07:20 < jonatack> (just launched the guix build; perhaps it will go faster for rc2)
07:24 < luke-jr> :/
07:24 < luke-jr> hopefully we won't lose many builders due to guix
07:25 < luke-jr> the point is to sign them, not necessarily to simply publish them
07:29 < laanwj> jonatack: fwiw rc2 build went really fast for me, everything but the build itself was cached
07:29 < laanwj> jonatack: one reason to do a rc2 build is to help testing this
07:30 < laanwj> please store the log, if it again takes 20 hours, we should take a look why
07:34 < jonatack> thanks, will let it run then. so far it does appear to be just building.  i figured guix rc1 taking that long was from having a slow vpn + slow laptop (+ more builds than previously with gitian signing iirc). gitian builds took ~6 hours without cache.
07:52 < sipa> jonatack: depending on what model you're using, a significant portion of the time may be building/downloading/installing build dependencies (guix packages), which you won't need to redo.for.rx2
07:53 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
08:00 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
09:07 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity]
10:01 < provoostenator> (I'm still strying to do this the hard way, if only to ensure that still results in the same deterministic result, but might take a while)
10:13 < laanwj> provoostenator: thanks for trying!
10:14 < laanwj> i've been doing the builds the lazy way: on a x86_64 VM running the GUIX distribution
12:23 < jonatack> guix-build for rc2 just finished
12:24 < jonatack> 5.5 hours, much better :D
12:24 < laanwj> jonatack: yess
12:51 < jonatack> yes if this time my codesigned don't conflict then it was smooth sailing, following hebasto's gist at https://gist.github.com/hebasto/7293726cbfcd0b58e1cfd5418316cee3 (thanks!)
12:53 < hebasto> jonatack: yw :)
12:57 < provoostenator> One dragon down, with help from dongcarl.  Let's see if the bootstrap finishes....
12:57 < dongcarl> :-)
13:01 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
13:03 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-builds
13:06 < achow101> is there a pr for the SHA256SUMS line endings issue?
13:07 < achow101> also, do we want to have the shasums include the directory names? that seems like bad UX as users will be downloading individual files and not the directory structure, so verifying SHA256SUMS would be slightly more difficult
13:11 < achow101> all of the files are uniquely named so it seems unnecessary to include the directory names
13:16 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
13:18 < jonatack> provoostenator: cool! (and congrats on the bitmex news, great to hear)
13:18 < provoostenator> jonatack: thanks!
13:33 -!- belcher [~belcher@user/belcher] has quit [Read error: Connection reset by peer]
13:45 -!- belcher [~belcher@user/belcher] has joined #bitcoin-core-builds
13:59 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
15:59 < dongcarl> Opened #22642 for separate SHA256SUMS{,.asc} files at release time
15:59 < gribble> https://github.com/bitcoin/bitcoin/issues/22642 | release: Release with separate SHA256SUMS and sig files by dongcarl · Pull Request #22642 · bitcoin/bitcoin · GitHub
17:27 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
18:27 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity]
19:30 -!- copumpkin [~woohoo@user/copumpkin] has quit [Quit: Textual IRC Client: www.textualapp.com]
19:36 -!- copumpkin [~woohoo@user/copumpkin] has joined #bitcoin-core-builds
20:14 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 265 seconds]
20:18 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
20:38 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 258 seconds]
20:39 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
20:42 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
20:47 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
--- Log closed Fri Aug 06 00:00:30 2021