[Bug]: cosmovisor released binaries - wrong files in the package

[dyasny]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

I downloaded and unpacked a release today:

wget https://github.com/cosmos/cosmos-sdk/releases/download/cosmovisor%2Fv1.5.0/cosmovisor-v1.5.0-linux-amd64.tar.gz
tar zxvf cosmovisor-v1.5.0-linux-amd64.tar.gz

Checked the sha256sums in the SHA256SUMS-cosmovisor-v1.5.0.txt file:

grep linux-amd64 SHA256SUMS-cosmovisor-v1.5.0.txt
7f4bebfb18a170bff1c725f13dda326e0158132deef9f037ab0c2a48727c3077  cosmovisor-v1.5.0-linux-amd64.tar.gz

And then checked the SHA256 sum of the unpacked binary:

 sha256sum ./cosmovisor
626dfc58c266b85f84a7ed8e2fe0e2346c15be98cfb9f9b88576ba899ed78cdc  ./cosmovisor

So there is a mismatch, moreover, if I run this binary:

cosmovisor version
cosmovisor version: (devel)
7:01PM INF running app args=["version"] module=cosmovisor path=/home/x/x/cosmovisor/genesis/bin/x
1.0.0

Cosmos SDK Version

cosmovisor 1.0/1.5

How to reproduce?

As above

[julienrbrt]

Hi! This is a known (Go) behavior. In order to get the correct version name you should install it via go install. There is a note in the documentation about it.

[dyasny]

@julienrbrt so you are saying I shouldn't rely on the releases and always build? Because I've never seen such behaviour with go builds.

[julienrbrt]

I am saying you should use go install. There are some closed issues about it that explains and demonstrate more.

[dyasny]

Understood, thanks