Skip to content

Conversation

Anipik
Copy link
Contributor

@Anipik Anipik commented Aug 31, 2021

Fixes #57982

@ghost
Copy link

ghost commented Aug 31, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #57982

Author: Anipik
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

Comment on lines +26 to 28
<PropertyGroup Condition="'$(PreReleaseVersionLabel)' == 'servicing'">
<IsShipping>false</IsShipping>
</PropertyGroup>
Copy link
Member

Choose a reason for hiding this comment

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

Does that mean that none of these packages ship during servicing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

they will get shipped internally

Copy link
Member

@ViktorHofer ViktorHofer Sep 1, 2021

Choose a reason for hiding this comment

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

Why do we change the definition of what's shipping publicly vs internally based on if the repo is in servicing mode?

Copy link
Member

Choose a reason for hiding this comment

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

What packages are these specifically? IsShipping generally controls whether something goes to NuGet. Are they supposed to go to NuGet in non-servicing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why do we change the definition of what's shipping publicly vs internally based on if the repo is in servicing mode?

basically following the same convention guidelines from the coreclr team as we did for 5.0.0

What packages are these specifically? IsShipping generally controls whether something goes to NuGet. Are they supposed to go to NuGet in non-servicing?

yes they are not supposed to go to nuget in non-servicing

Copy link
Member

Choose a reason for hiding this comment

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

But they do go in rtm? What package set is this specifically?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes they go to nuget in rtm, these https://github.com/dotnet/runtime/tree/main/src/coreclr/.nuget

Microsoft.ILVerification
Microsoft.NETCore.ILAsm
Microsoft.NETCore.ILDAsm
Microsoft.NETCore.TestHost
dotnet-ilverify

@Anipik Anipik merged commit a23a20b into dotnet:release/6.0 Sep 1, 2021
@Anipik
Copy link
Contributor Author

Anipik commented Sep 3, 2021

/backport to main

@github-actions
Copy link
Contributor

github-actions bot commented Sep 3, 2021

Started backporting to main: https://github.com/dotnet/runtime/actions/runs/1199414650

@github-actions
Copy link
Contributor

github-actions bot commented Sep 3, 2021

@Anipik backporting to main failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: fix stable package proj versioning support
Using index info to reconstruct a base tree...
M	src/coreclr/.nuget/Directory.Build.props
Falling back to patching base and 3-way merge...
Auto-merging src/coreclr/.nuget/Directory.Build.props
CONFLICT (content): Merge conflict in src/coreclr/.nuget/Directory.Build.props
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix stable package proj versioning support
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@ghost ghost locked as resolved and limited conversation to collaborators Oct 3, 2021
@Anipik Anipik deleted the stableInfra branch November 10, 2021 18:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants