Runtime: Mono runtime NuGet versions on blob storage

[filipnavara]

Since the merge of #33074 the new Microsoft.NETCore.Runtime.Mono packages are generated from CI pipelines in the dotnet/runtime repository with versioning matching the rest of packages. Unfortunately, previous builds from mono/mono CI pipelines were uploaded to the same blob storage and used different versioning strategy (ie. match Mono major.minor version and commit distance). The result is that automatic NuGet versioning would now pick the historic 6.x versions of packages instead of the 5.0.0-preview.2 ones which are newer.

[filipnavara]

[akoeplinger]

@dotnet/runtime-infrastructure can we easily delete these 6.x package versions from dotnetfeed.blob.core.windows.net?

[ViktorHofer]

I don't have permissions to do so but I believe @MattGal or @mmitche should have.

[MattGal]

I don't have permissions to do so but I believe @MattGal or @mmitche should have.

I have the permissions, but deleting packages from a sleet feed is not as simple as deleting the blob. One has to use their API to prevent messing up the manifests. @jcagme has experience with this and is coincidentally on FR this week so should be able to handle it.

[jcagme]

There are 1,037 6.x versions for Microsoft.NETCore.Runtime.Mono. Do you want all those removed?

[filipnavara]

@jcagme Yep, also the runtime.<rid>.Microsoft.NETCore.Runtime.Mono packages of which there is plenty.

[jcagme]

Ok. Doable but it will take up to days depending on how busy the feed is. I can provide status as things move forward.

[filipnavara]

It was broken for weeks (including the time the packages were not published after repository consolidation) so a day or few won't make a big difference. I am just happy that there is a way to resolve this. Thanks!

[mmitche]

They probably also need to be deleted from the .net 5 feeds..i'm guessing.

[filipnavara]

@mmitche Which feed is that? I don't think these NuGets were published to any other feed, at least not a public one.

[mmitche]

@mmitche Which feed is that? I don't think these NuGets were published to any other feed, at least not a public one.

dotnet5. https://dev.azure.com/dnceng/public/_packaging?_a=package&feed=dotnet5&package=Microsoft.NETCore.Runtime.Mono&protocolType=NuGet&version=6.11.0.265-preview

Btw, We're going to stop publishing to the dotnet-core feed soon, and the AzDO feeds will be the only feeds regularly getting new packages. That's what we should be telling customers to use for daily builds.

[filipnavara]

Btw, We're going to stop publishing to the dotnet-core feed soon, and the AzDO feeds will be the only feeds regularly getting new packages. That's what we should be telling customers to use for daily builds.

Uh, didn't know that, thanks for the heads up. I rely on the dotnet-core feed in quite a few projects.

[mmitche]

The dotnet5 and dotnet5-transport feeds (you probably only need dotnet5 if you're relying on shipping packages) have any of the new packages (from ~september onwards). See https://github.com/dotnet/arcade/blob/master/Documentation/CorePackages/Publishing.md#which-feeds-does-arcade-infra-publish-to

We're stopping publishing to the dotnet-core feed for a couple reasons:

• It's a 'fake' feed that has some crappy experiences when browsing for or downloading packages directly
• We already have to use AzDO feeds for any internal scenario (the blob feeds don't have authentication
• It's a pretty expensive feed to push to (a push from another repo at the same time locks the feed).

There was a preliminary mail sent yesterday to the dncpartners alias detailing the change.

[filipnavara]

Thanks for the explanation.

There was a preliminary mail sent yesterday to the dncpartners alias detailing the change.

As a non-Microsoftie I usually don't get those. I also rarely follow the changes on the arcade repository.

The reasoning for the change makes sense. Consider it a friendly reminder that people not on the list, or the .NET team, may be consuming the feed.

[jcagme]

400 Microsoft.NETCore.Runtime.Mono packages have been removed so far from the dotnet-core feed. ~600 to go. Then I'll work on the runtime.<rid>.Microsoft.NETCore.Runtime.Mono and check the .net 5 feeds

[jcagme]

Microsoft.NETCore.Runtime.Mono deletion completed. Moving to runtime packages now

[jcagme]

@filipnavara are runtime.<rid>.Microsoft.NETCore.Runtime.Mono packages in the same feed? Can you please give me the name of one?

[filipnavara]

@jcagme Yep. They are on the same feed. The affected packages seem to be:

• runtime.linux-arm64.Microsoft.NETCore.Runtime.Mono
• runtime.linux-x64.Microsoft.NETCore.Runtime.Mono
• runtime.osx-x64.Microsoft.NETCore.Runtime.Mono
• runtime.win-x64.Microsoft.NETCore.Runtime.Mono

Thanks!

[jcagme]

https://github.com/dotnet/arcade/pull/4838 complete, moving to runtime.linux-x64.Microsoft.NETCore.Runtime.Mono

[jcagme]

runtime.linux-x64.Microsoft.NETCore.Runtime.Mono done, onto runtime.osx-x64.Microsoft.NETCore.Runtime.Mono

[jcagme]

runtime.osx-x64.Microsoft.NETCore.Runtime.Mono done, closing with runtime.win-x64.Microsoft.NETCore.Runtime.Mono

[filipnavara]

Thanks a lot!

[jcagme]

runtime.win-x64.Microsoft.NETCore.Runtime.Mono is now deleted. Do we need to remove more packages?

[filipnavara]

I checked all the packages and there's still few broken versions on the feed:

runtime.linux-arm64.Microsoft.NETCore.Runtime.Mono:

• 6.7.0.282
• 6.11.0.236-preview

runtime.linux-x64.Microsoft.NETCore.Runtime.Mono:

• 5.3.0.1
• 5.3.0.2
• 5.3.0.3
• 5.3.0.5
• 6.11.0.236-preview
• 6.13.0.95-preview
• 6.13.0.99-preview

runtime.os-x64.Microsoft.NETCore.Runtime.Mono:

• 5.3.0.1
• 5.3.0.2
• 5.3.0.3
• 5.3.0.5
• 6.7.0.744-preview
• 6.9.0.99-preview
• 6.11.0.236-preview

runtime.win-x64.Microsoft.NETCore.Runtime.Mono:

• 5.3.0.5
• 6.11.0.236-preview

Microsoft.NETCore.Runtime.Mono

• 6.11.0.236-preview

[jcagme]

Done, can you please verify?

[filipnavara]

All the 5.3.x.x versions disappeared but I still see the rest.

[jcagme]

Where do you see the versions? When looking for a package in VS, looking at the blob feed, or?

[filipnavara]

NuGet Explorer when looking at the specific feed:

[sebastienros]

Here is the url that lists what is available: https://dotnetfeed.blob.core.windows.net/dotnet-core/flatcontainer/runtime.linux-x64.microsoft.netcore.runtime.mono/index.json

Note that nothing after April 5 has been added to the feed (which is a concern for me personally)

[filipnavara]

@sebastienros The primary feed has changed to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json. You should see new packages there.

Update: Actually I don't see new packages there either :-/ There were some name changes. @akoeplinger?

[sebastienros]

FYI here is the url listing all available versions on this feed, confirming anything after April 5th hasn't been added, and all 6.* version are available there.

https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/7d9f5c21-0d79-403f-bfe3-9a4506529760/nuget/v3/flat2/runtime.linux-x64.microsoft.netcore.runtime.mono/index.json

[jcagme]

Packages from https://dotnetfeed.blob.core.windows.net/dotnet-core should all be removed by now (please confirm if this is not the case). For the artifact feeds in Azure, I don't have any automation to delete packages.

[akoeplinger]

@filipnavara yes we stopped publishing these runtime.* packages in favor of runtime packs like https://dev.azure.com/dnceng/public/_packaging?_a=package&feed=dotnet5&package=Microsoft.NETCore.App.Runtime.ios-x64&protocolType=NuGet&version=5.0.0-preview.4.20213.12.

We haven't done the work yet to add runtime packs for desktop OS since we'll need to figure out how to distinguish between coreclr vs. mono there.