Unpin ASP.NET targeting pack for 3.0.1 servicing

[nguerrera]

Required change to ingest dotnet/aspnetcore#14425

@mmitche @livarcocc @JunTaoLuo @dougbu

[nguerrera]

Pinging this as a note that this change will still be needed once we have good 3.0.1 ASP.NET targeting pack

[nguerrera]

@JunTaoLuo

[nguerrera]

@mmitche

[nguerrera]

Re-pinging @livarcocc for review

[nguerrera]

@JunTaoLuo

   aspnetcore-targeting-pack-3.0 depends on dotnet-targeting-pack-3.0 (>= 3.0.1); however:
    Version of dotnet-targeting-pack-3.0 on system is 3.0.0-1.

The .deb for the ASP.NET tp requires version 3.0.1 of base tp, but we are keeping base tp pinned.

[dougbu]

@wtgodbe @JunTaoLuo is this now unblocked?

[nguerrera]

#5450 (comment)

[nguerrera]

Sorry, no, wrong branch. I'm not seeing a PR with a build with the fix for above...

[mmitche]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[nguerrera]

Did we get a new ASP.NET with the change to pin the ref pack, else this will fail again.

[mmitche]

Did we get a new ASP.NET with the change to pin the ref pack, else this will fail again.

Checking

[mmitche]

No. The last time an aspnetcore officail build passed was tueday

[JunTaoLuo]

There should be an update available since AspNetCore finished building. Does there need to be a manual trigger on this PR to ingest the new build?

[nguerrera]

I've incorporated this into #5526 that ingests the stabilized build