-
|
This discussion is being used to capture any issues related to the usage of the alpha versions for the various Chocolatey Components, that are going to support NuGet v3 feeds, as well as .NET Framework 4.8.
If you find an issue with any of these pre-release packages, please first check the known issues list below, and if it is not already covered, add an answer to the discussion below and we can discuss further. Known IssuesThe following lists, which will be added to as any new issues are discovered, are of known issues with the pre-release version of Chocolatey CLI, Chocolatey GUI, Chocolatey Licensed Extension, Chocolatey GUI Licensed Extension, and Chocolatey Agent. This is not intended to provide full details on the issues, but if more information is required to make things clear, please reach out and we can provide additional information.
Chocolatey CLI
2.0.0-beta-20230426
2.0.0-beta-20230412
2.0.0-beta-20230321
2.0.0-alpha-20230307
2.0.0-alpha-20230221
2.0.0-alpha-20230124
Chocolatey GUI2.0.0-beta-20230412
2.0.0-beta-20230412
2.0.0-beta-20230321
2.0.0-alpha-20230307
2.0.0-alpha-20230221
Chocolatey Licensed Extension6.0.0-beta-20230426
6.0.0-beta-20230412
6.0.0-beta-20230321
6.0.0-alpha-20230307
6.0.0-alpha-20230221
Chocolatey GUI Licensed Extension2.0.0-beta-20230426
2.0.0-beta-20230412
2.0.0-beta-20230321
2.0.0-alpha-20230221
Chocolatey Agent2.0.0-beta-20230426
2.0.0-beta-20230412
2.0.0-beta-20230321
2.0.0-alpha-20230221
|
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 24 replies
-
|
If the absolute latest version of a not installed dependency is prerelease, the prerelease version will be installed, even if there is a release version available that would satisfy the version contraints. Example: |
Beta Was this translation helpful? Give feedback.
-
|
@TheCakeIsNaOH thanks for bringing this up. During the last sprint of work, this issue has been addressed, and should be included within the next release. |
Beta Was this translation helpful? Give feedback.
-
|
2.0.0-alpha-20230307 seems to have broken installation from v3 sources, it just says "The source ... failed to get a NuGet.Protocol.Core.Types.ListResource resource" Not entirely sure what that means, but the source in question supports everything that is specified as "required" in NuGet V3 API documentation: https://learn.microsoft.com/en-us/nuget/api/overview#resources-and-schema Also works fine with 2.0.0-alpha-20230221 and 2.0.0-alpha-20230124. |
Beta Was this translation helpful? Give feedback.
-
|
The issue is here: 42df644#diff-e1f39f082ffc1bb9680326d3576b2dd1c175d3e3af3d74064a5fd700afedbd02R345-R347 The list resource is not required for v3 feeds, and they do not have a native list resource, instead, the list resources for v3 feeds point to the v2 list endpoint (if available). So the list resource cannot be assumed to be available, the availability needs to be checked. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the insight, cake! I would highly appreciate if Chocolatey 2.0.0 would support pure V3 servers since V2 has no documentation so I can't implement it for our package repository. |
Beta Was this translation helpful? Give feedback.
-
|
@Sainan what happens if you try: |
Beta Was this translation helpful? Give feedback.
-
|
I have just tested the suggestion above, and I can confirm that it works around the problem that you are seeing here. For the time being until we can get this fixed up, I would suggest that you either revert back to version 2.0.0-alpha-20230221 of the Chocolatey alpha, or you run: to disable the optimization feature that is currently causing you a problem. |
Beta Was this translation helpful? Give feedback.
-
|
A fix has been put in place for this problem, and it will be available in the next release of the Chocolatey CLI. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@maxihafer you are seeing an issue with upstream Mono: mono/mono#12406 Issue #2313 was relating to using |
Beta Was this translation helpful? Give feedback.
-
|
I'm a little confused. There is no beta version of the Docker image. |
Beta Was this translation helpful? Give feedback.
-
|
It was mentioned:
There is no Linux Docker image of v2.0.0-beta-20230321. |
Beta Was this translation helpful? Give feedback.
-
|
I'm running into an issue related to upper/lowercase that I cannot replicate on 1.x. Tested on If the package name does not conform with the actual This is problematic because Chocolatey Puppet Module uses this to check for newer versions when a package is set to
DISCLAIMER: We're using Using When using lowercase > choco.exe upgrade --noop 7zip -r
7zip|22.1|22.1.0|falseWhen using UPPERCASE > choco.exe upgrade --noop 7Zip -r
Chocolatey would have used NuGet to install packages (if they are not already installed):
7Zip
chocolatey-compatibility.extension v1.0.0
Progress: Downloading chocolatey-core.extension 1.4.0... 100%
chocolatey-core.extension v1.4.0
7zip.install v22.1.0
Would have run 'chocolateyInstall.ps1':
$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$filePath = if ((Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne $true) {
Write-Host "Installing 64 bit version" ; Get-Item $toolsDir\*_x64.exe }
else { Write-Host "Installing 32 bit version" ; Get-Item $toolsDir\*_x32.exe }
$packageArgs = @{
packageName = '7zip.install'
fileType = 'exe'
softwareName = '7-zip*'
file = $filePath
silentArgs = '/S'
validExitCodes = @(0)
}
Install-ChocolateyInstallPackage @packageArgs
Remove-Item $toolsDir\*.exe -ea 0 -force
$installLocation = Get-AppInstallLocation $packageArgs.softwareName
if (!$installLocation) { Write-Warning "Can't find 7zip install location"; return }
Write-Host "7zip installed to '$installLocation'"
Install-BinFile '7z' $installLocation\7z.exe
Progress: Downloading 7zip 22.1.0... 100%
7zip v22.1.0EDIT:
Does |
Beta Was this translation helpful? Give feedback.
-
|
@nrk-akjaer thank you for taking the time to raise this, and apologies for not getting back to you about this sooner! We have investigated this issue, and have been able to replicate the problem. We have a fix in place, and this will be included in the next release of Chocolatey CLI. #3157 Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
@gep13 I am super grateful! Thanks for all the hard work and effort you guys have done to bring the release of Chocolatey 2.0! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
@nrk-akjaer At this particular time, I can't express how much we (as in me, the Engineering Team and the wider Chocolatey Team) appreciate those kind words. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Weirdly enough, 2.0.0-beta-20230321 as well as subsequent versions still exibit the V3 sources issue:
2.0.0-alpha-20230221 continues to work fine. I should've probably validated this earlier, sorry. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think it will fail with the same error as you previously reported though, right? What error does it report? I suspect the issue here is the source name. Typically, a source name will not have any spaces or extra characters in it. Can you try with just: I am not sure I follow what you mean when you ask "on a different note, will this also work fine with upgrades?". Can you elaborate on this? |
Beta Was this translation helpful? Give feedback.
-
|
Assuming you mean I should do something like this: I do indeed get the same error:
For the upgrades, my understanding is that when upgrading it uses the sources as can be seen via |
Beta Was this translation helpful? Give feedback.
-
|
Are you able to provide a copy of the chocolatey.log file from running the command that is failing? No, Chocolatey CLI does not remember the source that a package was installed from. All of the Chocolatey CLI commands will either use the sources that are configured via the |
Beta Was this translation helpful? Give feedback.
-
|
Sure, but it does not contain much more information: However, I guess it does show you another way to repro: Also, where is the cache? I was trying to test the upgrade stuff with a different source but it has a faulty index.json cached, and deleting |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I have been doing some looking into this, and I believe we know what is going on, but we will need to make a code change in order to fix it. For now, you should be able to use the following: To install your package. The underlying issue is that when attempting to use more than one source, if any of them have a ListResource available, it will attempt to use that, which means that the MetadataResource that is available on your V3 feed isn't queried at all. That is why your package is not showing up when you attempt to install it. For V3 feeds, the HTTP Cache is stored at: |
Beta Was this translation helpful? Give feedback.
-
|
Was it intended to make the 2.0.0 release (https://github.com/chocolatey/choco/releases/tag/2.0.0)? It has no downloads and 2.0.0-beta-20230426 remains to be the latest version according to community.chocolatey.org |
Beta Was this translation helpful? Give feedback.
-
|
Version 2.0.0 has been released internally and will be released publicly soon. |
Beta Was this translation helpful? Give feedback.
-
|
Now that the stable releases of the Chocolatey products have shipped, I am going to close out this discussion. If you continue to run into problems, you can join in on this discussion: |
Beta Was this translation helpful? Give feedback.
Now that the stable releases of the Chocolatey products have shipped, I am going to close out this discussion.
If you continue to run into problems, you can join in on this discussion:
#3173