00:05:00 <iDunk> https://paste.ubuntu.com/p/c5KXzmSn6d/
00:05:55 <selsta> pls no
00:07:14 <iDunk> I get 3f2ea03affdc75ccccbee148d03af9ad92da4af012c91a84a447863aa48f5b36 here.
00:08:58 <selsta> ok got the same message
00:09:59 <selsta> db55aa2ac8c7b8d8f9e471c09b0d3b7214360e24e94558f120124a1b3d84b336  osslsigncode-1.7.1.tar.gz
00:12:21 <selsta> bitcoin uses osslsigncode 2.0 https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-build.py
00:13:24 <iDunk> It's a different SHA256 hash on every run here.
00:13:32 <elFado> why is tor gateway +q here?
00:14:49 <iDunk> It's not a tar.gz archive, it's a web page.
00:15:10 <selsta> I'm currently testing with the 2.0 version
00:15:42 <selsta> elFado: spam, though should get removed again
00:16:21 <elFado> somethingUniqueR: kastelo was a scam afaik
00:17:08 <selsta> why do we even use osslsigncode, we don't sign our .exe
00:18:12 <selsta> guess we can just delete that from gitian-build.py
00:22:56 <selsta> iDunk: I'm building now with line 97-100 removed
00:23:16 <selsta> would it be fine if everyone does that for this release or should we tag v0.17.2.1?
00:38:00 <selsta> removing line 97-100 does not change the resulting hashes so should be fine without retagging
00:38:45 <bugs_> built 0.17.2.0 on fedora with cmake -DMANUAL_SUBMODULES=1; make
00:38:58 <bugs_> regular make fails with Submodule 'external/miniupnp' is not up-to-date.
00:38:59 <bugs_> FYI
00:39:13 <iDunk> git submodule sync
00:39:17 <iDunk> git submodule update
00:44:05 <bugs_> ok those two seem to do the track after git checkout release-v0.17
00:44:10 <bugs_> trick
00:58:26 <bugs_> github lists boost dependency as 1.58 - has that changed?  now i see:
00:58:43 <bugs_> monero/tests/unit_tests/node_server.cpp:355:21: error: max_listen_connections is not a member of boost::asio::socket_base
00:58:49 <bugs_> i have boost 1.60
00:59:59 <bugs_> (i didn't see that error when i did cmake -DMANUAL_SUBMODULES=1
01:01:22 <selsta> that is in unit tests
01:01:35 <selsta> which afaik do not get build if you execute cmake manually
01:02:03 <bugs_> ah ok
01:05:17 <selsta> guess that is something we should fix
01:05:24 <selsta> so that minimum dependency is 1.58 again
01:17:11 <bugs_> i also tried to build with a private openssl 1.1.1k library and got a lot
01:17:24 <bugs_> of boost related ssl issues
01:17:36 <bugs_> tomorrow i'll try with a newer boost
01:17:40 <bugs_> thanks
02:04:37 <iDunk> https://paste.ubuntu.com/p/k3NnVqtSHP/
02:09:58 <selsta> iDunk: https://paste.debian.net/hidden/502c34a4/
02:10:02 <selsta> two don't match so far :/
02:10:35 <selsta> did you do apt-get update and apt-get upgrade? we had issues with a gcc update once
02:12:51 <iDunk> That host is always up to date.
02:23:54 <selsta> android hashes match again
02:48:12 <msaqvhsxtikq> FUK has bееn intеnsеly hostilе to Monеro for ovеr 4 yеars. Making minеrs for Monеro, making a pool for Monеro, making codе that Monеro copiеd, not using bugs to stеal millions from еxchangеs. Wow. Such grеat hostility.
04:49:51 <mj-xmr> selsta, may you point me to some info how to make such a reproducible build? I already was able to create a couple of "depends"
04:51:13 <mj-xmr> or iDunk
04:52:01 <mj-xmr> ./contrib/gitian/gitian-build.py ?
06:41:09 <diso> buenas tardes a todos
06:52:23 <mj-xmr> hola
09:53:23 <iDunk> mj-xmr: there's a README.md with instructions in contrib/gitian
10:03:45 <mj-xmr> Thanks
12:09:40 <mj-xmr> just a heads up re: boost. I see on Actions, that "Perfect-daemon" is building a fix for the Boost 1.58
12:23:22 <selsta> hmm it is already PRed I think
12:26:56 <sethsimmons> Should I reproduce 0.17.2.0 or wait?
12:27:02 <sethsimmons> Want to be sure before I kick it off.
12:34:40 <selsta> sethsimmons: I guess a third result would be helpful
12:35:00 <sethsimmons> I don't have my env anymore so will take some time
12:35:02 <sethsimmons> But I can
12:35:24 <selsta> 2 of my hashes don't match
12:35:27 <selsta> and I don't know how to proceed lol
12:35:43 <mj-xmr> I will prepare it for the next time.
12:40:35 <selsta> sethsimmons: you have to change the gitian-build.py like this: https://github.com/monero-project/monero/pull/7652/files
12:40:40 <selsta> before building
12:45:58 <sethsimmons> Ok will take a stab at that shortly
13:10:22 <sethsimmons> Running now with those lines removed
13:11:07 <selsta> mostly interested in linux hashes
13:15:04 <sech1> Running now too
13:15:21 <sech1> I had to reinstall everything from scratch, it's been a while since 0.17.1.9 :D
13:58:43 <scoobybejesus> my hashes: https://paste.debian.net/1192772/
14:07:33 <selsta> yours match iDunk
14:07:45 * selsta waits for more hashes
14:16:47 <gingeropolous> so whats the deal? is the thing all comboobled or can i just follow the same instructions as before?
14:17:09 * sethsimmons  < https://matrix.org/_matrix/media/r0/download/matrix.org/cUInGDHaFMOeaYXrkJtzcCii/message.txt >
14:17:16 <sethsimmons> Linux hashes ^
14:17:36 <selsta> sethsimmons: yours match mine again
14:17:46 <selsta> scoobybejesus: iDunk: did you have the old cache?
14:17:48 <sethsimmons> Yeah don't match scoobys
14:17:52 <sethsimmons> weird
14:18:03 <sethsimmons> Mine was completely from scratch, had never built on this host before
14:18:04 <selsta> both sethsimmons and me did it from scratch
14:18:12 <scoobybejesus> i did not do from scratch
14:18:33 <selsta> seems like "something" changed that causes inconsistencies if not done from scratch
14:18:34 <iDunk> I had the old cache.
14:20:45 <sethsimmons> I did this but edited the gitian-build.py: https://www.reddit.com/r/Monero/comments/heng91/cli_v01601_nitrogen_nebula_has_been_tagged_you/fvsbcuc/?utm_source=reddit&utm_medium=web2x&context=3
14:26:44 <mj-xmr> Silly question: do I need to follow this step: git clone git⊙gc:monero-project/gitian.sigs.git
14:26:46 <mj-xmr> ?
14:27:03 <sethsimmons> Only to push sigs in a PR
14:27:12 <sethsimmons> Not to generate the hashes and compare FWIW
14:27:20 <mj-xmr> thx
14:27:28 <sethsimmons> but pushing sigs via PR is important for those who can (I need to)
14:31:24 <Inge-> We are not at the point where I can deploy a docker container, git clone, build and get a hash?
14:31:36 <sethsimmons> Thats what this does
14:31:46 <sethsimmons> It's a script to automate that for you
14:31:55 <Inge-> ooooh
14:32:33 <sethsimmons> <sethsimmons "I did this but edited the gitian"> The steps here create the user needed, install dependencies, run the build script, and outputs all hashes
14:32:42 <mj-xmr> I'm building on one slow machine, but I will plug a faster one soon.
14:32:44 <sethsimmons> Just edit user and version to match
14:42:03 <Inge-> hm so still have to run gitian-build.py outside docker. I was kind of hoping it would be even more containerized so everything happened inside docker :)
14:43:45 <skkjwzowfjbp> For a community that prides itself on manipulating people, you can't manage a single guy that spends most of his time in his underpants :D
14:47:39 <mj-xmr> OK, building on my best horse as well.
14:48:00 <sech1> I'm still building somehow
14:48:06 <sech1> Previous builds took less time
14:51:05 <sethsimmons> <Inge- "hm so still have to run gitian-b"> All of the building does, but still have to setup the build env for Docker
14:51:24 <sethsimmons> But yes, would be nice to have a pre-built container image that can be run to build the latest tag
14:54:46 * sethsimmons  < https://matrix.org/_matrix/media/r0/download/matrix.org/IINKreGJmWYkUFZNKZkxgcaT/message.txt >
14:54:57 * sethsimmons  < https://matrix.org/_matrix/media/r0/download/matrix.org/sSiEzZnCEtSwObjDgSpETqjU/message.txt >
15:03:09 <sech1> my hashes: https://paste.debian.net/hidden/3a64f669/
15:03:17 <sech1> I don't remember how to build MacOS binaries
15:04:15 <selsta> https://www.irccloud.com/pastebin/d8AK4JFI/
15:04:20 <selsta> sech1: ^
15:06:45 <sech1> My linux hashes didn't match with scoobybejesus - did you edit gitian-build.py as was recommended?
15:07:30 <scoobybejesus> i commented out ilnes 97-100, yeah
15:08:17 <sech1> me too
15:08:35 <selsta> it seems to be an issue with the cache, maybe some compiler got updated or so
15:08:46 <sech1> But I screwed up and restarted the build several times before it ran smoothly
15:10:09 <selsta> mine: https://paste.debian.net/hidden/7dbf7c52/
15:12:21 <sech1> selsta your hashes match with mine. I'll start the build again to build MacOS binary
15:18:40 <sethsimmons> https://hub.docker.com/layers/sethsimmons/simple-monerod/v0.17.2.0/images/sha256-db1486b946f664c9c0e04a2feb5ee74add8bdfbe6f85df647f111f5a152d06d1?context=repo
15:18:52 <sethsimmons> Docker image pushed if anyone wants to test/get ahead of the game running it.
15:19:40 <sethsimmons> Still building reproducible hashes.
15:24:59 <selsta> I guess downloading some docker image to do the process for you also isn't ideal if you can't verify what the docker image does :D
15:25:08 <selsta> (not familiar with docker so I can be wrong here)
15:25:09 <Inge-> heh
15:25:27 <Inge-> well ideally there is a github page with a Dockerfile that is used in the creation of said image
15:25:41 <Inge-> so you can inspect the Dockerfile, and use it to build your own image
15:26:24 <sech1> Running v0.17.2.0 on my server already
15:27:55 <Inge-> are there release notes or something to see the main changes? or only commits at this point?
15:28:25 <selsta> https://github.com/monero-project/monero/compare/v0.17.1.9...v0.17.2.0
15:28:46 <sethsimmons> ```
15:28:56 * sethsimmons  < https://matrix.org/_matrix/media/r0/download/matrix.org/ueKOtRgluKNtMtfrNWXDdusL/message.txt >
15:29:33 <selsta> Inge-: mostly stability fixes
15:29:54 <Inge-> and some longer-term hardening against node attacks I presume
15:30:20 <selsta> not yet in this release
15:30:45 <Inge-> k
15:31:03 <sech1> I see quite a few P2P fixes from anon CCS
15:31:09 <sech1> in v0.17.2.0
15:31:40 <selsta> mostly seg fault / deadlock / race condition fixes
15:34:02 <sech1> Oh, and my little bugfix PR (7615) is there too
15:34:36 <selsta> GUI has more interesting changes this time
15:35:03 <selsta> .merge+ 7652 7653 7654 7655
15:35:03 <xmr-pr> Added
15:39:03 <selsta> have been running the anon CCS fixes for a while on multiple nodes and everything seems quite stable :)
15:39:15 <selsta> though v0.17.1.9 also had 70 days update for me
15:39:16 <Inge-> selsta: with or without banlist?
15:39:34 <sech1> do you mean 70 days uptime?
15:39:38 <selsta> yes
15:39:39 <selsta> typo
15:39:50 <selsta> or thought about the right word and wrote the wrong one lol
15:39:54 <sech1> yes, I've been running 0.17.1.9 non-stop pretty much since it was released
15:40:22 <selsta> Inge-: most with, 1 without
15:51:02 <sethsimmons> Final hashes: https://paste.debian.net/1192802/
15:55:51 <selsta> Inge-: release notes https://paste.debian.net/hidden/80c091c8/
15:56:31 <sethsimmons> "- Only print blocked nodes once with --enable-dns-blocklist (#7295)"
15:56:36 <sethsimmons> Thank God, my poor logs XD
16:00:43 <gingeropolous> im gettin this: /home/xmrchain/monero/tests/unit_tests/node_server.cpp: In lambda function:
16:00:43 <gingeropolous>      acceptor.listen(boost::asio::socket_base::max_listen_connections, ec);
16:00:56 <gingeropolous> when trying to compile 17.2
16:01:13 <selsta> gingeropolous: https://github.com/monero-project/monero/pull/7654/files
16:01:15 <selsta> or update boost
16:01:22 <selsta> but that's just test, you can ignore it
16:01:30 <selsta> daemon should built fine
16:01:35 <selsta> build*
16:01:41 <gingeropolous> k. danke
16:04:05 <mj-xmr> Hashes late into the show: https://paste.debian.net/1192805/
16:04:26 <sech1> selsta "7 people who worked ..." and the list has 9 people
16:04:51 <selsta> ty
16:08:12 <gingeropolous> xmrchain is on 17.2
16:09:56 <sech1> hashes from me, this time with MacOS binaries: https://paste.debian.net/hidden/6d92502e/
16:10:11 <selsta> sech1: please post to gitian.sigs repo
16:10:19 <selsta> if you have gpg installed :D
16:10:34 <sech1> I don't...
17:33:37 <CSDUMMI[m]> Does anyone here know of a secure implementation of Ring Signatures. Specifically traceable Ring Signatures?
17:37:24 <moneromooo> Monero's implementation is meant to be secure. At least for Monero's usage.
17:57:32 <kinghat[m]> i know you guys are busy atm but maybe someone has help: https://github.com/monero-project/monero-gui/issues/2806#issuecomment-816019049
17:57:32 <kinghat[m]> > Can an @monero-project maintainer comment on why there is a requirement for a git clone in order to run make release as noted in the README.md file??
18:00:04 <moneromooo> That's how it determines the version string. I don't think there's another reason.
18:28:00 <mj-xmr> kinghat[m], I'd propose to clone from a local repository.
18:28:42 <mj-xmr> So clone from outside their build system, pass the cloned local copy to the BS, and from within clone the passed one.
18:29:16 <mj-xmr> You're not the issue starter, are you?
18:31:21 <kinghat[m]> no sorry, am just following along as I think monero should be packaged in flatpak for Linux.
18:32:51 <moneromooo> I think best would be to add a NO_GIT_VERSION cmake option.
18:33:19 <moneromooo> Set that and it uses... "unknown" as a version string.
18:33:34 <mj-xmr> I replied him. No problem.
18:37:34 <Inge-> thanks selsta
18:44:13 <kinghat[m]> thanks for the replies all