8000 Fix malformed NuGet.config file by NikolaMilosavljevic · Pull Request #550 · dotnet/dotnet · GitHub
[go: up one dir, main page]

Skip to content

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

Merged
merged 3 commits into from
May 15, 2025

Conversation

NikolaMilosavljevic
Copy link
Member
@NikolaMilosavljevic NikolaMilosavljevic commented May 14, 2025

Fixes: dotnet/source-build#5122

NuGet.config file in msbuild repo is malformed. packageSourceMapping element is incorrectly placed under packageSources element. Package source mappings in this, and the file modified by our tasks, are never used by Nuget, causing intermittent failures with NETStandard.Library being picked up from previously-source-built source, instead of reference source.

packageSourceMapping section was originally added with dotnet/msbuild#11255

Fixing in VMR instead of msbuild repo, to get this fixed asap.

@NikolaMilosavljevic NikolaMilosavljevic requested review from a team May 14, 2025 16:48
@MichaelSimons
Copy link
Member

Fixing in VMR instead of msbuild repo, to get this fixed asap.

Please loop in the appropriate msbuild folks to review.

@NikolaMilosavljevic
Copy link
Member Author

PR checks are hitting known NuGet Audit errors - will likely need to wait until #546 is merged before rerunning checks.

@NikolaMilosavljevic
Copy link
Member Author

@rainersigwald @baronfel it would be great to have a review from someone on the msbuild repo side.

Copy link
Member
@baronfel baronfel left a 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.

8000
@baronfel
Copy link
Member

Logged a bug on the NuGet side asking for some more validation in NuGet.config to prevent these kinds of errors.

@ViktorHofer ViktorHofer enabled auto-merge (squash) May 15, 2025 07:36
@JanProvaznik
Copy link
Member

Does the dotnet/dotnet -> dotnet/msbuild flow work already? or should I copy the commit to MSBuild manually?

@ViktorHofer
Copy link
Member

Already works. Should come in tomorrow morning with the backflow subscription: dotnet -> msbuild (main)

@ViktorHofer ViktorHofer merged commit f7f6723 into dotnet:main May 15, 2025
11 checks passed
@rainersigwald
Copy link
Member

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)?

@mthalman
Copy link
Member

Yes, I believe so.

@mthalman
Copy link
Member

@NikolaMilosavljevic is out this week, btw

@MichaelSimons
Copy link
Member

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)?

Confirming @mthalman's response of Yes, I believe so,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Intermittent poison test failure: Value is not null
7 participants
0