' MacBook-Pro-de-alex:gitian-builder alex$ [16:41:14] Hmmm [16:42:12] Let me dump my VM and create a totally fresh one (The one I was testing on was not totally fresh, it had already been setup to build nav locally) [16:42:24] Maybe it's just some system tool that's missing [16:47:25] https://cdn.discordapp.com/attachments/416000318149754881/575725454577893396/unknown.png [16:47:36] is this output correct? [17:03:41] yeah [17:03:46] Looks correct [17:14:19] getting the same [17:19:58] Hmm [17:20:06] I'm confused [17:20:14] BRB, gonna get a coffee so I can think 😄 [17:53:58] Wew [17:54:04] I did a completely fresh setup [17:54:17] Seems it's caused by not having ruby on the machine running docker [17:55:21] Updated instructions: sudo apt install ruby docker -y cd /tmp rm -rf gitian-builder git clone https://github.com/devrandom/gitian-builder.git rm -rf navcoin-core git clone https://github.com/mxaddict/navcoin-core.git --branch=patch-5 cd gitian-builder ./bin/make-base-vm --docker --arch amd64 --suite bionic USE_DOCKER=1 ./bin/gbuild --commit navcoin-core=patch-5 --url navcoin-core=https://github.com/mxaddict/navcoin-core.git [17:55:21] ../navcoin-core/contrib/gitian-descriptors/gitian-win.yml [17:55:27] @aguycalled try that [17:58:25] ruby was already installed [17:58:32] Hmm [17:58:40] same result as before [17:59:46] Now I'm really confused [17:59:56] You think it's possible to start a tmate session? [18:00:11] Just create a user with no permissions [18:00:29] And run a tmate session in it so I can connect [18:00:55] All I need is a tmate session with a user that can use /tmp DIR [18:01:56] i can give you access, do you have a ssh key [18:02:11] Yeah [18:02:41] ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDIy4ISm3m0c1JMHWtaNIoctniuYsfFeK0Ar2mJluLuQsG/OpvxTFK6R99R2mhmz7s9ZXjC922Gi+uxWv8FhJ8xf4lS7H7K4I4F/k4uyvpetp35d2ct+zuAN0jixbcHfNGJlZRzIk6yhkv4yjapvTmcQzFrKc/tYm1mz12MDi9L3ozzyIxhsW3U8PvvS909M8dZIuJZoV0KyoUkoslFQQqAIFYsDSB4FNLv9PXBna2CdxBtbym7fMTD8fYWM8UZ493lXFufRPaN/k+TZG3DPylWqiRYnQQUpq2sxBX9Kov/kcNA9oJinJiWoBE0bNRGi+zeqOICZiyncG2wWbjWoy3Z mxaddict@mxaddict-blade [18:04:21] pm [18:09:21] I'm logged in [18:12:00] https://cdn.discordapp.com/attachments/416000318149754881/575746742796943369/Screenshot_from_2019-05-09_02-11-46.png [18:12:08] It's working 😄 [18:13:53] And I tailed var/build.log docker@build:/tmp/gitian-builder$ tail var/build.log ^ ./google/protobuf/stubs/common.h:382:11: note: in definition of macro ‘GOOGLE_COMPILE_ASSERT’ msg[bool(expr) ? 1 : -1] ^~~ /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/home/ubuntu/build/navcoin-core/depends/i686-w64-mingw32/native/include [18:13:54] -pthread -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -c -o google/protobuf/stubs/structurally_valid.lo google/protobuf/stubs/structurally_valid.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/home/ubuntu/build/navcoin-core/depends/i686-w64-mingw32/native/include -pthread -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -c google/protobuf/stubs/structurally_valid.cc -o [18:13:54] google/protobuf/stubs/structurally_valid.o /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/home/ubuntu/build/navcoin-core/depends/i686-w64-mingw32/native/include -pthread -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -c -o google/protobuf/descriptor.lo google/protobuf/descriptor.cc [18:14:02] So it's building now [18:15:17] And here is bash history: 14 cd /tmp 15 rm -rf gitian-builder 16 git clone https://github.com/devrandom/gitian-builder.git 17 rm -rf navcoin-core 18 git clone https://github.com/mxaddict/navcoin-core.git --branch=patch-5 19 cd gitian-builder 20 ./bin/make-base-vm --docker --arch amd64 --suite bionic 21 USE_DOCKER=1 ./bin/gbuild --commit navcoin-core=patch-5 --url [18:15:18] navcoin-core=https://github.com/mxaddict/navcoin-core.git ../navcoin-core/contrib/gitian-descriptors/gitian-win.yml 22 history [18:15:28] Those are the only commands I ran [18:15:31] And it worked [18:15:53] I stoped the build @aguycalled can you try it now? [18:16:03] The files are in /tmp [18:17:27] https://cdn.discordapp.com/attachments/416000318149754881/575748113059545090/unknown.png [18:17:51] https://cdn.discordapp.com/attachments/416000318149754881/575748212288127023/unknown.png [18:18:53] 🤷 [18:19:04] ??? [18:19:08] Hahaha [18:21:42] copy pasted from your history [18:43:07] Hahaha [18:43:17] I'm so confused [18:46:28] I've sshed again [18:46:32] And I tried again [18:46:37] Seems to work again for me [18:46:39] LOL [18:46:50] Let me start a tmux session, and can you connection? [18:46:58] I'll show you what I mean [18:47:28] just connect to tmux a -t 0 on the docker user on that server [18:47:33] Let me know once connected [18:47:39] I'll show you what I mean [18:52:09] @aguycalled I have one last thing that I can think of why it does not work [18:52:25] Can you run groups and show me what groups your user has? [18:52:40] its on docker group [18:52:46] Hahaha [18:52:51] So then, I'm out of idea [18:52:59] i can't use tmux i'm using byobu [18:53:07] Ohh [18:53:52] Does byobu conflict with the tmux shortcut keys? [18:54:10] I mean, can't you ssh to server, then run tmux a -t 0 on the docker user? [18:56:15] im in @mxaddict [18:57:09] Hmmm [18:57:13] Tmux crashed? [18:57:14] LOL [18:57:17] i closed, sorr [18:57:18] y [18:57:22] Ohh [18:57:22] 😄 [18:57:28] looks like the problem is byobu [18:57:33] But looks like it worked 😄 [18:57:34] Hahaha [18:57:47] if i try out of byobu it works too [18:57:50] But why would a terminal/window manager cause that issue? [18:57:58] some env variable? [18:58:03] IDK how that's even possible when SSHed [18:58:05] Hmmm [18:58:09] You have a point 😄 [18:58:19] Do you have RVM on your byobu? [18:58:27] I mean on the machine running byobu [18:58:48] Cause I've seem that cause problems with some of my servers when I run TMUX on local, then ssh to a server [18:59:35] The way I solved the issue was to also add RVM on the server [18:59:43] I mean, if that's even the issue here [19:00:40] Anyways, I guess just not use byobu for the builds 😄 Hahaha [19:00:49] Let me know how it goes from here on. [19:01:02] installed rvm, trying now [19:01:13] Nice [19:01:21] same [19:01:27] inside of byobu it does not work [19:01:56] It must be something either related to ruby or docker [19:02:14] Since those are the only 2 things that are run from the host [19:02:24] Everything else is run inside of docker [19:02:53] some sort of config/env value that is being carried over the SSH session [19:03:39] Maybe you can try printenv [19:03:59] And compare the output for a byobu vs normal terminal [19:04:08] when connected to server [19:06:43] @mxaddict have you tried building using gitian for every os already? [19:06:53] does it work without these steps? [19:06:54] https://cdn.discordapp.com/attachments/416000318149754881/575760557303529493/unknown.png [19:07:02] Yes, osx and windows working [19:07:17] Linux/Arm has an issue with glibc and gcc symbols check [19:08:01] No, I have not tried with signed builds [19:08:08] I've only tested unsigned [19:10:38] I;ve built osx using MacOSX10.11.sdk.tar.gz [19:10:47] That was hosted on bitcoin.org I think [19:12:30] OSX_SDK="10.11" curl --location --fail $SDK_URL/MacOSX${OSX_SDK}.sdk.tar.gz -o depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz [19:13:19] That is the SDK that I used [19:22:53] what is you guys are doing that you're having a problem resolving? [19:23:02] something about hashes? [19:23:11] yep, non deterministic builds [19:23:21] is it just md5 sums? [19:24:00] i've seen md5sum computer a different hash for the EXACT same file on 2 different computers [19:24:08] the build process should be deterministic so everyone can replicate it and verify hashes, looks like @mxaddict is quite close to solve it [19:24:15] was baffling but i never looked into what causes it [19:25:25] I just need to fix the linux build (check-symbols) and we should be ready for review [19:25:37] the use case was i was running md5sum on the same config on multiple servers as a Zabbix monitoring check to determine if the file had changed. so i can md5sum from the command line on a bunch of the servers and a few of them had different md5sums for the same file with the same EXACT contents with the SAME EXACT package versions, kernel version, etc. [19:25:40] Since I got windows and osx builds working on my machine [19:25:47] And I could repeaat the same hashes [19:25:51] sha256sum results [19:30:38] @prole @aguycalled are you against updating our MAX glibc and GCC to newer versions? [19:30:58] no, im not [19:31:08] This would fix the issue I'm having with patch-5 branch on linux builds check-symbols build step [19:31:10] i guess those would be lined with upstream [19:31:23] i mean, bitcoin-core [19:31:31] If we do update the MAX version, that means our builds won't work on older linux boxes [19:31:41] how old? [19:31:59] I think the wallets we build would stop working with < 14.04 [19:32:25] I will need to check the versions, but I think will work with ubuntu 14.04 and up for ubuntu [19:32:32] And Debian 8 and up [19:32:53] For other distro's not sure what Glibc they ship with [19:32:54] older systems can always buildthemselves [19:33:00] id go forward with it [19:33:10] Ok, I will make the changes [19:33:14] Test then push once ready 😄 [19:33:32] 14.0 is ancient [19:33:44] Yeah [19:33:51] Half a decade 😄 [19:33:55] systems running 14.04 are probably low on RAM as well [19:58:34] 14.04 just passed its LTS [20:13:39] *** Joins: aguycalled (~user@unaffiliated/aguycalled) [20:13:43] *** Server sets mode: +cnt [20:29:31] https://github.com/NAVCoin/navcoin-core/issues/473 [20:29:46] @mxaddict [20:30:35] Ok, will do [20:30:49] when we added curl because of navtech i was not able to make gitian work for every os when linking static [20:31:08] i leave up to you what is better 😉 [20:32:20] I'll see which is less friction [20:32:42] If it's too hard to get libcurl on all platforms then we should scrap it [20:33:09] But if I can fix it via the Makefiles, then we should keep it :D [20:33:46] Looks like that is gonna be yet another set of changes to be added to my PR [20:34:03] That PR with the build and Lib updates is getting big [20:34:04] Hahaha [20:34:14] Harder to review what I've changed [21:24:06] 2 prs paid as theyve been merged @mxaddict [21:31:32] Thanks [21:31:46] BTW, navexplorer seems stuck on block 3111664 [21:34:49] @prole what do you think of this: https://github.com/NAVCoin/navcoin-core/issues/471#issuecomment-490414883 [21:35:14] Those are the steps for building using docker 😄 [21:38:34] nice, i can try it here if you want [21:38:58] p.s. the conversation around the repo name, what do we want to do? rename the organisation to "navcoin" all in lower case [21:39:44] I think the Organization can stay NAVCoin [21:39:47] afaik github links are not case sensitive. [21:39:49] https://github.com/NAVCoin/navcoin-core [21:39:53] https://github.com/navcoin/navcoin-core [21:39:54] But the url should be "navcoin" [21:40:12] so either should work [21:40:18] No, they are not, but it ticles my OCD 😄 [21:40:24] lol [21:40:29] It's up to you guys though [21:40:34] okay, so i will change it so the URL is lower case [21:40:43] Yey [21:40:44] 😄 [21:40:58] we have to rename the organisation in this case [21:40:59] https://help.github.com/en/articles/renaming-an-organization [21:41:08] Hmmm [21:41:09] most things should transfer over / redirect [21:41:10] We do? [21:41:22] If we do, then I think we should leave it [21:41:42] Display Name will still == NavCoin [21:41:54] but the URL will change from NAVCoin to navcoin [21:42:06] and mentions will be @navcoin [21:42:29] it should be fine [21:42:33] Ok [21:42:41] I'll update my PR 😄 [21:42:44] since i dont think github cares about capitalisation anyway [21:43:02] Yeah, that's cause they use ruby for the router [21:43:33] I think they still use parts or the rails router which was not case sensitive last time I used it [21:43:44] okay, there we go it's lower case how [21:43:47] *now [21:43:51] Wew! 😄 [21:44:00] can you update your PR and ill approve it [21:44:01] Now that is REAL progress [21:44:02] Hahaha [21:44:06] lol [21:44:13] hey ive closed like 3 prs this morning bro [21:44:15] im trying [21:44:19] 😛 [21:44:22]