Closed BClark09 closed 7 years ago
@BClark09 will the new version once again be called "2.1.0-1"? Maybe the -1 can be left out this time?
@ThomDietrich Unfortunately, it cannot:
"version": "2.1.0",
"release": "1"
The packager does this automatically for .deb convention, even if version 2.1.0 is specified it will automatically add the release number to the end. I don't think I can alter this.
If you apt-cache madison [PackageName]
for most packages, you'll see the same thing.
apt-cache madison openhab2
openhab2 | 2.0.0-1 | https://dl.bintray.com/openhab/apt-repo2 stable/main amd64 Packages
apt-cache madison git
git | 1:2.11.0-3 | http://ftp.uk.debian.org/debian stretch/main amd64 Packages
git | 1:2.11.0-3 | http://ftp.uk.debian.org/debian stretch/main Sources
apt-cache madison maven
maven | 3.3.9-4 | http://ftp.uk.debian.org/debian stretch/main amd64 Packages
maven | 3.3.9-4 | http://ftp.uk.debian.org/debian stretch/main Sources
apt-cache madison iceweasel
iceweasel | 52.2.0esr-1~deb9u1 | http://security.debian.org stretch/updates/main amd64 Packages
iceweasel | 45.9.0esr-1 | http://ftp.uk.debian.org/debian stretch/main amd64 Packages
firefox-esr | 45.9.0esr-1 | http://ftp.uk.debian.org/debian stretch/main Sources
firefox-esr | 52.2.0esr-1~deb9u1 | http://security.debian.org stretch/updates/main Sources
RPM versions don't use this convention, so are naturally left as 2.1.0
Interesting. Thanks for the explanation. No further comments ;)
PR can wait unmerged until release, then after Cloudbees can run
buildLatestRelease
Signed-off-by: Ben Clark ben@benjyc.uk