Hi all,

I'm trying to get a vote out for the 0.16.0 binaries, but I'm running into
some issues publishing the binaries. I'm wondering if those who have done
this in the past have any advice.

The problem seems to boil down to this: when I upload the tarball generated
by the release-candidate script, bintray does not give me the option to
explode it. Uploading it directly via curl, rather than the UI, I get an
error back telling me that it's not a valid type of file to explode, for
some reason it reads it as an octet-stream rather than a tarball (I even
tried forcing it by specifying a Content-Type header on the curl request to
no avail).

If I change the release-candidate script to generate a tar.gz instead of a
.tar, then I am able to get bintray to give me the option to explode the
archive, however it still fails because for some reason it's trying to sign
the files in the archive, but the signature is already present. I've
confirmed that the option to GPG sign files is not selected for my
repository.

At this point I'm at a loss for how to continue, as there does not seem to
be any way to upload the binaries and have bintray explode them, which is
required for the binary to actually be usable.

You can see what I've uploaded in its current tar form here:
https://dl.bintray.com/jcohen/aurora/

Any advice is appreciated!

Cheers,

Joshua

Reply via email to