-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peng/389 release 0.4 #422
Peng/389 release 0.4 #422
Conversation
Blocking
|
Update: Fixed
|
So to summarize, using But You can confirm this by seeing that Finally: the binary built following the release docs by @mappum works! I can run it and make an account and stake. Just the |
I am very sorry. There was a commit missing in the deterministic-zip PR. The important part was, that the packed executable didn't have the rights to execute. I readded this. |
On devtools: You can set |
My Linux-build SHA256: 757dab38d271cb2fcaa516052d76e530bea80c872f22061889135bcdc67ccd5d |
@faboweb thanks! I have an error related to
|
Sadly tar-fs doesn't produce deterministic builds. |
@faboweb It looks like the macOS build works with your warning bypassing the error. One minor issue is that using |
Cosmos-darwin-x64_0.4.0.tar.gz
Cosmos-linux-x64_0.4.0.tar.gz
Cosmos-win32-x64_0.4.0.zip
|
Sadly the checksums are not equal :( Cosmos-darwin-x64_0.4.0.tar.gz
Cosmos-linux-x64_0.4.0.tar.gz
Cosmos-win32-x64_0.4.0.zip
Regarding |
I created a follow up issue here: #424 |
Got the same hashes as Peng when building with his Veriability isn't a blocker for this release though, we'll just have to get it working before launch. |
tar.gz
by usingtar-fs
instead oftar-stream
Please follow the release docs and confirm these hashes for me: WIP
Closes #389