Pre-release version of created RPM packages don't sort correctly

[troian]

Describe the bug

nfpm package replaces - to _ which seems to break RPM version guidelines

https://www.thegeekdiary.com/understanding-rpm-versions-and-naming-schemes

Reproduce

Try create packages with versions v1.1.1_beta1 and v1.1.1_beta2. Install v1.1.1_beta1 followed by update to v1.1.1_beta2 which is ignored

[caarlos0]

I was looking into this... this is as intended, actually: #24

it won't accept 1.2.3-beta1 as a version...

afaik there is no way to add a "prerelease" tag to the version to the rpm spec... but I'm not well versed in RPM so I may be wrong...

[troian]

Found this sort of explanation https://serverfault.com/a/867567

Server Fault

Incremental RPM package version "numbers" for x.y.z > x.y.z-beta (or alpha, rc, etc)

In order to publish RPM packages of several different versions of some software, I'm looking for a way to specify version "numbers" that are considered "upgrades", and include the differentiation of

[djgilcrease]

This should be fixed by #79 so long as you use a version like v1.2.3-0.1.beta

[caarlos0]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.