08:40:13 <selsta> tobtoht_: should we revert the patch that introduced the test failure? or does it appear easy to fix?
08:52:47 <m-relay_> <o​frnxmr:xmr.mx> valldrac
11:45:52 <tobtoht_> selsta: it's an edge case that only affects those tests. we shouldn't use (mainnet) checkpoints there, because we're mining from genesis.
11:46:01 <tobtoht_> not initializing checkpoints if we're running tests or simply ignoring checkpoints below height 1k would fix the issue
11:47:45 <m-relay_> <o​frnxmr:xmr.mx> Does it effect something like testnet?
11:56:25 <m-relay_> <o​frnxmr:xmr.mx> (More specifically, an alpha testnet for fcmp (mined from genesis))
12:25:37 <tobtoht_> no, realistically only affects regtest unless alpha testnet exceeds 1M blocks and checkpoints are never updated
12:28:35 <m-relay_> <o​frnxmr:xmr.mx> thanks
13:19:29 <m-relay_> <a​non_contributor_xmr:monero.social> Hey, what is the current status of reproducible builds with guix?
13:19:29 <m-relay_> <a​non_contributor_xmr:monero.social> I have tried it on two different machines and it successfully built the same binaries (also it was quite easy to setup and run, as opposed to gitian which I have tried a few times but gave up after a few failed attempts..), so I am wondering why is it not included in the release branch, are there any problems/blockers with it that I am unaware of?
13:20:27 <m-relay_> <o​frnxmr:xmr.mx> Its on master only
13:22:16 <m-relay_> <a​non_contributor_xmr:monero.social> Yeah I noticed that, hence my question - why is it only on master branch, and not in the release branch, are there any problems with it?
13:22:39 <m-relay_> <t​obtoht:monero.social> we'll branch from master somewhere in the coming months
13:23:33 <m-relay_> <t​obtoht:monero.social> no problems with it. backporting to release would have gotten too complicated
13:25:46 <m-relay_> <a​non_contributor_xmr:monero.social> Good to know that there are no problem with it :) Why is backporting complicated? I wanted to use it to experiment with building Monfluo reproducibly, but I guess it will not be as easy as taking contrib/guix (plus dependencies like contrib/shell) from the master branch? :(
13:27:25 <m-relay_> <t​obtoht:monero.social> nope, unfortunately. it depends on dozens of changes to contrib/depends
13:27:37 <m-relay_> <o​frnxmr:xmr.mx> Just use master
13:27:40 <m-relay_> <a​non_contributor_xmr:monero.social> Ah got it :(
13:27:41 <m-relay_> <a​non_contributor_xmr:monero.social> Thanks for the info!
13:27:52 <m-relay_> <o​frnxmr:xmr.mx> nothing wrong with using master for monfluo
13:29:10 <m-relay_> <a​non_contributor_xmr:monero.social> I think I would rather just wait until guix gets into a release branch, it is not a huge priority for me right now :)
13:29:52 <m-relay_> <o​frnxmr:xmr.mx> It will be branched from master when it does :P. only diff is a tag
13:31:38 <m-relay_> <o​frnxmr:xmr.mx> (release hasnt been branched from master in years now. When guix hits release, it will be the first time we've branched master in yrs)