Skip to content

Conversation

@eerhardt
Copy link
Member

The subset host.pkg is not producing the DotNetHost* NuGet packages. This is because the "Pack" target is getting invoked on the pkgprojs, but pkgprojs expect the "Build" target to be called. Since the "Pack" target is overriden in the Directory.Build.targets to be empty, no one is calling the "Build" target on the pkgprojs.

In an official build, a later subset packs.tests comes through and builds Microsoft.DotNet.CoreSetup.Packaging.Tests.csproj, which explicitly calls "Build" on the pkgprojs. So official builds still get these packages produced.

In source-build, we are no longer building the packs.tests subset, so the packages are not produced.

The subset `host.pkg` is not producing the DotNetHost* NuGet packages. This is because the "Pack" target is getting invoked on the pkgprojs, but pkgprojs expect the "Build" target to be called. Since the "Pack" target is overriden in the Directory.Build.targets to be empty, no one is calling the "Build" target on the pkgprojs.

In an official build, a later subset `packs.tests` comes through and builds `Microsoft.DotNet.CoreSetup.Packaging.Tests.csproj`, which explicitly calls "Build" on the pkgprojs. So official builds still get these packages produced.

In source-build, we are no longer building the `packs.tests` subset, so the packages are not produced.
@ghost
Copy link

ghost commented Oct 18, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

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

Thanks. Shouldn't this target 6.0 given that the dead-line is approaching?

@eerhardt
Copy link
Member Author

eerhardt commented Oct 18, 2021

Shouldn't this target 6.0 given that the dead-line is approaching?

I assume it is "too late" for 6.0.0 now. @Anipik?

The change has the risk of breaking the official build in 6.0.0, so I wanted to get it into main first to ensure it works both in PR validation and official build.

I was just going to patch this in for 6.0.0 source-build, and get the change included in the first servicing release - 6.0.1.

@ViktorHofer
Copy link
Member

For main the long term fix is to switch away from pkgproj to the NuGet Pack task, tracked via dotnet/arcade#7783.

@eerhardt
Copy link
Member Author

/backport to release/6.0

@github-actions
Copy link
Contributor

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1356397959

@ViktorHofer
Copy link
Member

This is because the "Pack" target is getting invoked on the pkgprojs, but pkgprojs expect the "Build" target to be called.

nit: Since dotnet/arcade@74cdaee, the above statement is technically not true anymore as the Pack target - as long as it's not overridden, which it is in this case - is a fine entry point as well.

@Anipik
Copy link
Contributor

Anipik commented Oct 18, 2021

I assume it is "too late" for 6.0.0 now. @Anipik?

we can get the change in if its safe

@Anipik
Copy link
Contributor

Anipik commented Oct 18, 2021

cc @mmitche

@eerhardt eerhardt merged commit 9824543 into dotnet:main Oct 19, 2021
@eerhardt eerhardt deleted the FixInstallerPackages branch October 19, 2021 17:52
@ghost ghost locked as resolved and limited conversation to collaborators Nov 18, 2021
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.

6 participants