> # for now, chocolatey does only support SemVer v1 (no dot separated identifiers in pre-release)
preview4and it will work
@kachbit: You would need to install Chocolatey as a non-administrative install:
Alternatively, if you have Chocolatey for Business, you could look into self service:
Hello all. I have just tried to install a package hosted at GitHub but I have run into a problem and noticed another issue while trying to resolve it.
First: the URL for the release is incorrect in the install script. This means it fails with 404. The package is FreeCAD 0.19.1, and although the chocolatey status page for this package says it has passed the tests, and was approved on March 21. The release was made on March 12. I cannot find anything in the FreeCAD git history that would suggest why the URL is incorrect or changed, so I suspect it may lay with the auto update (au) fetched by the bot. The difference in the URL is merely "-1" appended to the binary name at FreeCAD's repo. Is this a known issue with other packages?
Second: The download counter for packages on the web page seems to only count the number of installation scripts fetched and does not register whether the package payload itself was fetched successfully (see above) Is this expected or intended?
@Squelch: The freecad package is maintained at the coreteam repository, and there is an issue about the invalid url here:
It is an issue with the freecad package specifically, and not other packages.
The download count on the community repository is a count of the number of times that the
.nupkg package file has been downloaded.
Choco open source does not have telemetry/data collection that reports back to Chocolatey.org, so there is no way for the community repository to know the statistics of if a package install failed or not. The download of the freecad installer comes from github, not from Chocolatey.
@thecakeisnaoh:naoh.host kann you help my with my sharegate-desktop 14.2.0 update? I has changed the IconUrl and the download URL for the new release and the checksum.
The local installation test was successfully but the automated testing was failed.
Unfortunately, I can not understand the problem.
.nuspecof the Chocolatey package, and then it hopefully will work.
--package-parameters-sensitive, note that this requires a licensed edition of choco.
In chocolatey is version 8.1.0-preview5 higher than 8.1.0-preview42 ? (trying to fix a preview version without affecting the stable version on the same feed)
The screenshot seems to indicate yes - assuming processing against a feed will be identical - but I don't like to assume and it isn't covered here: https://docs.chocolatey.org/en-us/create/create-packages#package-fix-version-notation
choco search powershell-core -pre -s $pwdI was able to prove that locally a preview fix version will work as I am formatting - if I got it wrong - please drop a line.
Restored code coverage metrics initially for currect choco/swupd: https://github.com/tapika/swupd
20% based on chocolatey.tests.dll. Need to try to run on integration tests as well, if it will work.