Repository navigation
Fix prerelease version naming of building packages of PSCore6 #5846
Description
The version should have been 6.0.0~beta.1 instead of 6.0.0-beta.1. The final version will be 6.0.0-1 which is alphabetically behind all the current prerelease versions so apt install powershell installs 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
Activity
[-]Fix prerelease version of building packages of PSCore6[/-][+]Fix prerelease version naming of building packages of PSCore6[/+]SteveL-MSFT commentedon Jan 11, 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
SteveL-MSFT commentedon Jan 11, 2018
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.
iSazonov commentedon Jan 13, 2018
I propose to consider GitVersion
iSazonov commentedon Jan 29, 2018
From above link the highest priority recommendation is:
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.
iSazonov commentedon Mar 12, 2018
Fixed in #6318