ocm-linux-amd64 from the release page for 0.1.57 doesn't seem to work properly #319
Comments
|
@mmazur reported the same |
|
The binaries are corrupted. |
|
Looks like the binaries have been partially uploaded. I am checking. Meanwhile I am removing them from the releases page. |
jhernand
added a commit
to jhernand/ocm-cli
that referenced
this issue
Sep 23, 2021
The action that publishes releases was uploading artifacts using the `--data` option of the `curl` tool. That results in processing them as ASCII and limits the size to approximately 4 MiB. The end result is that the uploaded binaries don't work. This patch fixes that using the `--data-binary` option instead. Related: openshift-online#319 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
jhernand
added a commit
to jhernand/ocm-cli
that referenced
this issue
Sep 23, 2021
The only change in this relase is that the _GitHub_ action that publishes releases has been fixed so that it publishes correct binaries. There are no changes in functionality. See https://github.com/openshift-online/ocm-cli/issues/319[#319] for details. Related: openshift-online#319 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
Merged
|
This has been fixed in release 0.1.58. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I downloaded the binary on a couple of different machines (Fedora 34, RHEL 7), and when I run it it just seems to output several pages of unprintable characters. It's almost as if it's
cating itself to stderr, but that's probably not what's happening.It also seems that I consistently get a different sha256 for the file than what's listed in the corresponding sha256 file.
@jhernand am I doing something silly?
The text was updated successfully, but these errors were encountered: