01:45:19 when you use dockrun.sh it doesn't really matter what your host is, since gitian-builder.py is running inside its own ubuntu 18.04 docker container 02:30:34 i suspected, but didn't want to do an upgrade i couldn't easily undo 18:15:37 tag is up 18:51:10 starting a build 18:55:06 hyc https://paste.debian.net/1271217/ 18:57:41 i put my scrollback at 55k lines.. hehe... tried to paste the entire 55k and it was rejected as too large 18:58:59 i've never seen that on any of my runs 18:59:38 remember that the container is initialized with your directory tree where you're running from 18:59:51 perhaps you have some large data.mdb or core files in your source tree 19:04:42 i haven't committed anything. i generally change no source anyway. hm. since the last run, all i did was cd to monero, git pull (the only change seems to be the tag), cd .. , paste the builder script, and run it with --docker other normal options. 19:09:08 do a "git status" anyway? 19:09:21 see what other untracked files are sitting around 19:17:55 modified: contrib/gitian/dockrun.sh (to print a var i was curious about) and modified: external/randomx (new commits) 19:19:27 otherwise, on master, up to date, those are not staged for commit, and no changes are staged. pretty plain tree 19:23:11 any envoy / grpc experts in here for a haveno-related problem? please let me know 19:25:13 just a +echo $GH_USER change to dockrun. and that was added after suffering from the spam. anyway, i will let you know if i figure out something 19:27:54 I've started a build too 19:29:01 ditto 20:39:08 my checksums: https://paste.debian.net/hidden/6dc9cd6e/ 20:40:54 hashes from github actions: https://github.com/monero-project/monero/actions/runs/4208839881 20:41:53 matches 20:41:54 wow 20:44:42 https://github.com/monero-project/gitian.sigs/pull/234 20:45:02 selsta should I upload my binaries for you? 20:45:26 or you can just download from github actions, I guess 20:46:56 yep, will download them from github, less work for you 20:48:55 running v0.18.2.0 on my nodes now 21:47:53 who needs layer2 solutions when we have sech1, so fast, thank you