bundlers icon indicating copy to clipboard operation
bundlers copied to clipboard

Incorrect versions in some bundler outputs

Open sellout opened this issue 2 years ago • 2 comments

It looks like some bundlers are dropping the leading 0. for pre-1.0 versions.

Here it is for a project of mine – the toDEB and toRPM results both say the version is 1.0, while toDockerImage has the correct 0.1.0 version.

$ nix bundle --bundler github:NixOS/bundlers#toDEB
$ nix bundle --bundler github:NixOS/bundlers#toDockerImage
$ nix bundle --bundler github:NixOS/bundlers#toRPM
$ ls *bash-strict-mode*
bash-strict-mode-0.1.0.tar.gz

deb-single-bash-strict-mode/:
.  ..  bash-strict-mode_1.0_amd64.deb

rpm-single-bash-strict-mode/:
.  ..  bash-strict-mode-1.0-1.x86_64.rpm
$ 

sellout avatar Nov 30 '22 18:11 sellout

How do I control the versions on the deb and rpm bundlers anyway?

I have a bunch of binaries that get correct versions when the normal wrapped binaries are produced, but rpm and deb just put 1.0: https://github.com/fedimint/fedimint/releases/tag/v0.3.0-rc.2

dpc avatar Mar 25 '24 16:03 dpc

Ah! That might be the actual problem – not that the leading component is dropped, but that RPMs and DEBs always get 1.0.

sellout avatar Mar 25 '24 16:03 sellout