11:36:28 <xiphon> luigi1111w: could you please update monero submodule to the current master head again?
11:37:37 <xiphon> ^ Windows build needs (463d044f5e49a1ab409d235f421dda6f0363c4c4 commit) boost 1.73 fix
11:43:44 <xiphon> ah, on the other hand i will just include monero submodule update in Windows CMake workflows PR (will push it soon)
11:53:26 <xiphon> luigi1111w: so nevermind
12:12:13 <selsta> .merge+ #2927
12:12:13 <xmr-pr> Added
12:15:26 -xmr-pr- selsta opened pull request #2927: DaemonManager: remove max-concurrency upper bound
12:15:27 -xmr-pr- > https://github.com/monero-project/monero-gui/pull/2927
13:01:06 <binaryFate> I'm curious about the setup being used for compiling static binaries for release, and in particular how easy it is to reproduce the environments? For instance is there an ansible way to recreate them or anything alike?
13:03:04 <selsta> I can write a tutorial for macOS
13:03:30 <selsta> don’t know about Win / Linux
17:37:09 <binaryFate> GUI Nitrogen Nebula is online :) https://web.getmonero.org/downloads
18:32:28 <kinghat[m]> \o/j
18:32:33 <kinghat[m]>  * \o/
19:07:33 <selsta> luigi1111w: release notes for github https://paste.debian.net/hidden/427cf902/
19:07:36 <selsta> ErCiccione[m]: ^^
19:08:57 <ErCiccione[m]> Thanks for the ping. I will make the post tomorrow
20:39:21 <xiphon> binaryFate: there is no step-by-step guide to reproduce the environment for compiling static Monero GUI binaries
20:40:10 <xiphon> i plan to implement Docker container producing static Linux binaries
20:42:42 <xiphon> ^ i.e. one command to build static Linux release 
20:43:33 <xiphon> given that Dockerfile will contain all the environment configuration steps, this could be used as a guide as well
20:44:17 <xiphon> (we still have to migrate to CMake first what i'm working on right now)
20:44:22 * xiphon afk
20:45:27 -xmr-pr- xiphon opened pull request #2928: workflows: Windows CMake 'release-win64' target CI
20:45:27 -xmr-pr- > https://github.com/monero-project/monero-gui/pull/2928
22:12:22 <selsta> .merge+ #2928
22:12:22 <xmr-pr> Added
22:12:43 <selsta> xiphon: should we set -j2 / -j3 for cmake gui?
22:13:47 <selsta> (linux / mac: -j3 and windows: -j2)
22:19:31 <binaryFate> Ok thanks xiphon
22:20:36 <binaryFate> If not for trust, at least for efficiency would be nice to have a recipe of some sort, so if a machine/environment is lost, we can setup / reproduce a new one easily
22:20:50 <binaryFate> until we have reproducible builds
22:40:09 <xiphon> selsta: aright, will update #2928
22:41:53 <selsta>  https://paste.debian.net/hidden/3fccda5a/
22:41:59 <selsta> btw this is currently where it fails on macOS
22:42:13 <selsta> it got to ~87%