01:56:44 should we be updating the version of OpenSSL in our builds? 1.0 is deprecated 01:58:46 newest OpenSSL security advisory (today) https://www.openssl.org/news/secadv/20201208.txt 03:16:04 bah. cmake can't find this version of openssl 03:16:06 pos 06:21:17 inv4 "Monero developer Howard Chu suggests switching to Proof of Stake with a one-line comment on IRC: pos" 06:21:23 *inb4 10:41:14 https://twitter.com/moneroisthebest/status/1336620468548366337 11:02:19 Why does the Saviour of NASA take a group achievement award and present it as a proof of individual glory? https://twitter.com/hyc_symas/status/1203709575226183683 11:32:36 so, apparently github is introducing a new "discussions" tab, where people could discuss things without open issues. Sounds interesting, could be a good alternative to /r/monerosupport (i have no idea how it works yet) 11:33:57 https://github.com/monero-ecosystem/monero-translations/discussions 11:35:00 looks interesting, like a mini-forum to suggest/discuss ideas and features 11:35:01 seems like a stackexchange kind of thing 12:14:14 Actually, they recently added some features, like dark mode and more detailed github actions: https://github.blog/2020-12-08-new-from-universe-2020-dark-mode-github-sponsors-for-companies-and-more/ 18:27:23 seems like our gitian builds are a bit fragile, downloading additional pkgs from ubuntu repo on top of the base docker image 18:27:35 because the ubuntu repo may age out and disappear 18:28:03 we should instead grab all pkgs we need right now and freeze that in a new docker image 18:28:11 no? 18:28:28 TheCharlatan: wdy think? 18:40:13 hello, I think we've identified a reproducible builds issue in monero: 18:41:35 please share 18:42:09 it seems that if a new release is pushed the code that generates the version string generates a different string, so rebuilding old versions would be a problem 18:42:34 this was flagged by the rebuilder system we use for archlinux: https://reproducible.archlinux.org/api/v0/builds/10997/diffoscope 18:43:47 `0.17.1.5-release` vs `0.17.1.5-3942a1cd` in the rebuild 18:43:54 wtf is a Gnu Build ID 18:44:29 you can ignore that, it's deterministic and going to be the same if there are no other differences in the binary 18:46:02 the version strings have a different length, so the diff is a bit noisy because the offsets are different in the rebuild 18:47:08 The "release" part of the version string checks if there is a commit which is a parent to the current HEAD. 18:47:23 I think that's what you mean with "if a new release is pushed". 18:49:10 it checks if you're building the most recent tagged commit 18:49:27 so it won't set "release" if you're building an older tagged commit 18:49:37 perhaps that should be changed 18:51:02 yes, what hyc is saying 18:51:11 I'm reaonably sure it will not say release if your HEAD is tagged but there's a child to HEAD. 18:51:29 That bugged me for my TF builds before. 18:52:19 I think the first package was built before the 0.17.1.6 release and the second one afterwards 18:58:41 we could use something like "git describe" instead, to determine if we're on a tagged commit 18:58:59 I'll try to fix it. 19:05:44 should I open an issue for this on github? 19:05:56 ndorf: see 7102, I remember this being fiddly and I might have broken your test case. 19:06:08 I don't think it's needed, there's a patch already. 19:06:13 (7102) 19:06:45 cool, thanks! 19:15:20 -xmr-pr- moneromooo-monero opened pull request #7102: cmake: fix "release" version string on tagged releases 19:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7102 23:42:46 moneromooo: do you mean the unit test? not sure how this change could break that, as it still seems to output either $ver-release or $ver-$commit as before? 23:43:12 I mean the make bit. 23:43:22 cmake 23:43:44 I'm not sure what you fixed it for, so I'm not sure whether I broke that fix. 23:51:48 oic. this should be good. the original fix was for not updating the string on incremental rebuild, this shouldn't affect that. i'll make sure 23:52:21 Ah. Yes, should not matter here. Thanks. 23:54:45 np, thanks for the heads up