Skip to content

Remove auditSources section #42706

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

Conversation

NikolaMilosavljevic
Copy link
Member

Nuget.client introduced source auditing with #42658, see NuGet/NuGet.Client#5939

This breaks source build, offline legs, as we do not use any online sources in those scenarios, and do not have internet access, see: dotnet/source-build#4548

This PR adds a patch, to remove auditSources section. - doing this to quickly unblock the VMR build.

Will create an issue to track the actual fix, to dynamically remove this section in VMR build.

@NikolaMilosavljevic NikolaMilosavljevic requested review from a team as code owners August 13, 2024 19:12
@ghost ghost added Area-Infrastructure untriaged Request triage from a team member labels Aug 13, 2024
@NikolaMilosavljevic
Copy link
Member Author

Date: Tue, 13 Aug 2024 18:57:27 +0000
Subject: [PATCH] Remove auditSources section

Tracking: https://github.com/dotnet/source-build/issues/4548
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For future reference the convention is Backport: as documented in the patch guidance. Also the referenced issue/PR should track the work to remove the patch. This issue was just closed by this PR. What issue is tracking the long term fix?

@mthalman
Copy link
Member

/backport to release/9.0.1xx

Copy link
Contributor

Started backporting to release/9.0.1xx: https://github.com/dotnet/sdk/actions/runs/10420699365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants