-
Notifications
You must be signed in to change notification settings - Fork 171
Fix malformed NuGet.config file #550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Please loop in the appropriate msbuild folks to review. |
PR checks are hitting known NuGet Audit errors - will likely need to wait until #546 is merged before rerunning checks. |
@rainersigwald @baronfel it would be great to have a review from someone on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, the fact that this isn't a validation error of some kind is kind of huge. Good find.
Logged a bug on the NuGet side asking for some more validation in NuGet.config to prevent these kinds of errors. |
Does the dotnet/dotnet -> dotnet/msbuild flow work already? or should I copy the commit to MSBuild manually? |
Already works. Should come in tomorrow morning with the backflow subscription: dotnet -> msbuild (main) |
It looks like this is breaking our official build on toolset restore; am I correct that @NikolaMilosavljevic's #554 would let us revert this change (and then fix forward shortly)? |
Yes, I believe so. |
@NikolaMilosavljevic is out this week, btw |
Confirming @mthalman's response of Yes, I believe so, |
Fixes: dotnet/source-build#5122
NuGet.config
file inmsbuild
repo is malformed.packageSourceMapping
element is incorrectly placed underpackageSources
element. Package source mappings in this, and the file modified by our tasks, are never used by Nuget, causing intermittent failures withNETStandard.Library
being picked up frompreviously-source-built
source, instead ofreference
source.packageSourceMapping
section was originally added with dotnet/msbuild#11255Fixing in VMR instead of
msbuild
repo, to get this fixed asap.