09:49 <htsbot> [discord] <flole998> https://help.cloudsmith.io/docs/upload-package#:~:text=Uploading%20to%20Cloudsmith%20is%20simple,as%20the%20official%20Cloudsmith%20CLI).

09:50 <htsbot> [discord] <flole998> Check out the postman example

17:11 <mint_headend> I see. I was following the directions on the repo page[~], which did not indicate needing to specify a version field.

17:11 <mint_headend> [~] https://cloudsmith.io/~tvheadend/repos/tvheadend/upload/#formats-deb or such

17:13 <mint_headend> Either way, the version script isn't working right since the GH actions artifacts debs have the same `0.0.0-unknown` version. I'll see about sending the version to cloudsmith once I have a good version to send.

17:13 <mint_headend> But for now I have no idea why the script isn't producing the right version.

19:48 <mint_TVH> The version script fails because I have no git tags.

20:24 <mint_TVH> With a tag, everything now works properly: https://cloudsmith.io/~tvh-cs-testing/repos/tvh/packages/.

20:26 <mint_TVH> Why do some of the workflows call cloudsmith from the YAML and others use the support/cloudsmith.sh script?

20:28 <mint_TVH> Oh, also, no need for passing a version field. Cloudsmith reads that from the package itself just fine.

22:54 <htsbot> [discord] <flole998> Because.... 😄 I think I added the yaml first, it caused issues on many platforms (all non x64 I think) so I wrote the beautiful script. Feel free to submit a PR with your changes, then we can test if it works in practice aswell

23:27 <mint_TVH> Will do.

23:46 <mint_TVH> Oops, I misread something. All workflows use the script; I thought some did and some didn't.

23:48 <mint_TVH> I do see though that `upload-cloudsmith` is an separate step for `build-rpm-native` and `build-rpm-native`, but not `build-raspberry` or `build-crosscompile`. Why the inconsistency? If none, can I make it an independent step for all of them?

23:48 <mint_TVH> * is an separate step for `build-deb-native` and `build-rpm-native`