You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We maintain GitHub actions runners and receive an issue about resolving packages from Nuget.or recently actions/runner-images#3038
It turned out that after invoking any choco command a nuget.config file is created in $env:APPDATA\NuGet\ and this file doesn't contain any NuGet package sources, which leads to msbuild failures because nuget currently respects user-wide config file — NuGet/NuGet.Client#3907 and there is no available sources in the file, created by choco.
It was reported in the chocolatey/choco repository, but the fix will actually be addressed here. The other issue will be kept open in order to flow into the release notes that are generated for Chocolatey itself.
gep13
added a commit
to gep13/nuget-chocolatey
that referenced
this issue
May 5, 2021
As Chocolatey, we never want to create the NuGet.Config file, as this is
not used by Chocolatey at all. As such, rather than GetOrCreateDocument,
if the filepath doesn't exist, simply return the default empty
XDocument, which is exactly what would have been returned after creating
the file.
The existing coding style has been adhered to here, and as little
changes as possible have been made.
As Chocolatey, we never want to create the NuGet.Config file, as this is
not used by Chocolatey at all. As such, rather than GetOrCreateDocument,
if the filepath doesn't exist, simply return the default empty
XDocument, which is exactly what would have been returned after creating
the file.
The existing coding style has been adhered to here, and as little
changes as possible have been made.
What You Are Seeing?
We maintain GitHub actions runners and receive an issue about resolving packages from Nuget.or recently actions/runner-images#3038
It turned out that after invoking any choco command a
nuget.config
file is created in$env:APPDATA\NuGet\
and this file doesn't contain any NuGet package sources, which leads to msbuild failures because nuget currently respects user-wide config file — NuGet/NuGet.Client#3907 and there is no available sources in the file, created by choco.$env:APPDATA\NuGet\nuget.config
content:What is Expected?
$env:APPDATA\NuGet\nuget.config
file is not createdHow Did You Get This To Happen? (Steps to Reproduce)
Output Log
Full Log Output
The text was updated successfully, but these errors were encountered: