-
Notifications
You must be signed in to change notification settings - Fork 136
[VMR] nuget-client build fails on case-preserving filesystems (Mac, Windows) #3149
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
Comments
[Triage] A fix was accepted in Arcade to address the problem that required the patch. We believe the source-build patch can now be removed. |
Is there a plan to remove the patch from the nuget-client repo? This is still causing build failures on non-Linux:
|
Yes, that is what we intend to do with this issue. |
@MichaelSimons what's the status on getting this resolved in nuget-client.git? This patch continues to break building on case-preserving filesystems (i.e. breaks Windows & Mac builds of the VMR) |
Taking a brief look, I don't think this is necessary anymore. I just ran a full vmr build to confirm. I will check a few more things and then open a PR to remove this. |
Alright I think I found the fix that eliminated the need for this patch - dotnet/arcade#7549. I will open a PR to remove this. |
OK. I can send a PR to NuGet.Client to remove https://github.com/NuGet/NuGet.Client/blob/dev/eng/source-build-patches/0001-Rename-NuGet.Config-to-NuGet.config-to-account-for-a.patch |
I just opened NuGet/NuGet.Client#5414 |
This patch has been removed and flowed into the VMR. |
On Linux,
NuGet.config
andNuGet.Config
are different files. Both can exist in the same folder, and attempts to read the "wrong" file will result in a file not found error. As a result, we have a patch in the NuGet repo,eng/source-build-patches/0001-Rename-NuGet.Config-to-NuGet.config-to-account-for-a.patch
authored by @crummel, to reconcile a bad casing assumption. However, on Windows and Mac, this patch fails to apply withgit apply
as those two filenames are considered equivalent. This breaks the build on non-Linux.We either need a way to separate out source build patches by OS applicability (e.g.
eng/source-build-patches/$(TargetOS)/
), or need to eliminate the patch.The text was updated successfully, but these errors were encountered: