Repository navigation
Fix prerelease version naming of building packages of PSCore6 #5846
Description
Activity
- added this to the milestone
on Jan 10, 2018 - changed the title
[-]Fix prerelease version of building packages of PSCore6[/-][+]Fix prerelease version naming of building packages of PSCore6[/+]on Jan 10, 2018 We're well aware of this and working on a solution. I believe if you specify the exact version it works. The naming we chose (and hence this issue) results in RC2 being "newer" than 6.0.0
chuanjiao10 it's not that simple. We've already removed the prerelease pkgs from packages.microsoft.com, but there is caching going on. Also for the RPM, if you have RC2 installed, it thinks that's newer so by default doesn't allow you to install 6.0.0. Current plan is to re-release 6.0.0 as 6.0.1 which should resolve this issue.
I propose to consider GitVersion
From above link the highest priority recommendation is:
Some upstreams assign their prereleases sortable numbers (that no other normal release will obtain). For example, sssd-1.8.0beta2.tar.gz is defined to be “1.7.92”. Use Version: 1.7.92 (in .spec file).
So for PowerShell Core 6.1.0 GA we could use the scheme: "unreal" version starting with 10000 - etc. 6.0.1000. We could consider 10001 - alpha1, 10002 - alfa2, 20001 - beta1, 20002 - beta2, 30001 - rc1. It allow continue use information suffixes for all package managers.
It seems the schema resolve all problems. We could easily implement it.Fixed in #6318
The version should have been
6.0.0~beta.1instead of6.0.0-beta.1. The final version will be6.0.0-1which is alphabetically behind all the current prerelease versions soapt install powershellinstalls rc2 instead of final.The convention for prerelease versioning is taken from http://gazebosim.org/tutorials?tut=install_unstable&cat=install
same for RPMs https://en.opensuse.org/openSUSE:Package_naming_guidelines