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

i suspected, but didn't want to do an upgrade i couldn't easily undo

tag is up

starting a build

hyc paste.debian.net/1271217

i put my scrollback at 55k lines.. hehe... tried to paste the entire 55k and it was rejected as too large

i've never seen that on any of my runs

remember that the container is initialized with your directory tree where you're running from

perhaps you have some large data.mdb or core files in your source tree

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.

do a "git status" anyway?

see what other untracked files are sitting around

modified: contrib/gitian/dockrun.sh (to print a var i was curious about) and modified: external/randomx (new commits)

otherwise, on master, up to date, those are not staged for commit, and no changes are staged. pretty plain tree

any envoy / grpc experts in here for a haveno-related problem? please let me know

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

I've started a build too

ditto

my checksums: paste.debian.net/hidden/6dc9cd6e

hashes from github actions: github.com/monero-project/monero/actions/runs/4208839881

matches

wow

selsta should I upload my binaries for you?

or you can just download from github actions, I guess

yep, will download them from github, less work for you

running v0.18.2.0 on my nodes now

who needs layer2 solutions when we have sech1, so fast, thank you