Skip to content

[master] Update dependencies from dotnet/sdk#9064

Merged
dotnet-maestro[bot] merged 9 commits intomasterfrom
darc-master-4cce5096-36fd-4b94-ba12-5d198a821a27
Nov 17, 2020
Merged

[master] Update dependencies from dotnet/sdk#9064
dotnet-maestro[bot] merged 9 commits intomasterfrom
darc-master-4cce5096-36fd-4b94-ba12-5d198a821a27

Conversation

@dotnet-maestro
Copy link

@dotnet-maestro dotnet-maestro bot commented Nov 12, 2020

This pull request updates the following dependencies

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

  • Coherency Updates:
    • Microsoft.AspNetCore.App.Ref: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • Microsoft.AspNetCore.App.Ref.Internal: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • Microsoft.EntityFrameworkCore: from 6.0.0-alpha.1.20509.5 to 6.0.0-alpha.1.20560.6 (parent: Microsoft.AspNetCore.App.Runtime.win-x64)
    • Microsoft.AspNetCore.App.Runtime.win-x64: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • dotnet-dev-certs: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • dotnet-user-secrets: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)
    • dotnet-watch: from 6.0.0-alpha.1.20526.6 to 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk)

From https://github.com/dotnet/sdk

  • Subscription: 6f9c7b2d-c29c-4b2f-fcec-08d7d0f045ee
  • Build: 20201116.1
  • Date Produced: 11/16/2020 10:28 PM
  • Commit: 8c0f92a
  • Branch: refs/heads/master

Microsoft.DotNet.MSBuildSdkResolver , Microsoft.NET.Sdk
 From Version 6.0.100-alpha.1.20561.16 -> To Version 6.0.100-alpha.1.20561.17

Dependency coherency updates

Microsoft.AspNetCore.App.Ref,Microsoft.AspNetCore.App.Ref.Internal,VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0,Microsoft.EntityFrameworkCore,Microsoft.AspNetCore.App.Runtime.win-x64,dotnet-dev-certs,dotnet-user-secrets,dotnet-watch
 From Version 6.0.0-alpha.1.20526.6 -> To Version 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk
@mmitche
Copy link
Member

mmitche commented Nov 12, 2020

@ViktorHofer @jkoritzinsky ... le sigh.

@ViktorHofer
Copy link
Member

frustrating to say the least. I agree...

Who can help with that? cc @dsplaisted and @nkolev92 for the nuget issue.

@Pilchie
Copy link
Member

Pilchie commented Nov 12, 2020

👀

@mmitche
Copy link
Member

mmitche commented Nov 12, 2020

I think I got it. Updated to 6.0 SDK and updated the target framework.

@mmitche
Copy link
Member

mmitche commented Nov 12, 2020

@dsplaisted @wli3 Any idea why dotnet tool install is attempting to install a net5.0 compatible SDK test package?

##[error]EXEC(0,0): error NU1202: (NETCORE_ENGINEERING_TELEMETRY=Build) Package testSdkClean 6.0.100-alpha.1.20561.17 is not compatible with net5.0 (.NETCoreApp,Version=v5.0) / any. Package testSdkClean 6.0.100-alpha.1.20561.17 supports: net6.0 (.NETCoreApp,Version=v6.0) / any

@mmitche
Copy link
Member

mmitche commented Nov 13, 2020

Looks like installer itself needs a stage0 update so that it attempts to restore from 6.0...trying to figure out how to make that ahppen.

@mmitche
Copy link
Member

mmitche commented Nov 13, 2020

@dsplaisted Apparently the fix was not as I thought. Locally a 6.0 targeting SDK worked but not here. Can you help?

Microsoft.DotNet.MSBuildSdkResolver , Microsoft.NET.Sdk
 From Version 6.0.100-alpha.1.20561.16 -> To Version 6.0.100-alpha.1.20563.2

Dependency coherency updates

Microsoft.AspNetCore.App.Ref,Microsoft.AspNetCore.App.Ref.Internal,VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0,Microsoft.EntityFrameworkCore,Microsoft.AspNetCore.App.Runtime.win-x64,dotnet-dev-certs,dotnet-user-secrets,dotnet-watch
 From Version 6.0.0-alpha.1.20526.6 -> To Version 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk
@mangod9
Copy link
Member

mangod9 commented Nov 16, 2020

Is there an ETA on merging this? This is required for getting osx-arm64 layouts working. Thx.

Microsoft.DotNet.MSBuildSdkResolver , Microsoft.NET.Sdk
 From Version 6.0.100-alpha.1.20561.16 -> To Version 6.0.100-alpha.1.20566.1

Dependency coherency updates

Microsoft.AspNetCore.App.Ref,Microsoft.AspNetCore.App.Ref.Internal,VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0,Microsoft.EntityFrameworkCore,Microsoft.AspNetCore.App.Runtime.win-x64,dotnet-dev-certs,dotnet-user-secrets,dotnet-watch
 From Version 6.0.0-alpha.1.20526.6 -> To Version 6.0.0-alpha.1.20561.2 (parent: Microsoft.NET.Sdk
@Pilchie
Copy link
Member

Pilchie commented Nov 16, 2020

Also blocking dotnet/aspnetcore's perf testing. @marcpopMSFT - can we prioritize getting this merged asap?

@wli3
Copy link

wli3 commented Nov 16, 2020

I'll look into this.

@wli3
Copy link

wli3 commented Nov 17, 2020

for some reason dotnet.dll (from dotnet/sdk) still has assembly attribute

[assembly: TargetFramework(".NETCoreApp,Version=v5.0", FrameworkDisplayName = "")]

@wli3
Copy link

wli3 commented Nov 17, 2020

ah. still stage 0 issue. We use stage 0 to build, build stage 0 use older dotnet.dll. And the new dotnet.dll is part of the payload, so we need to break the cycle.

@wli3
Copy link

wli3 commented Nov 17, 2020

I'll just disable the tool tests to get a build, and reenable it once it is done. It is not too bad considering we only have the problem once a year @marcpopMSFT @dsplaisted

@dotnet-maestro dotnet-maestro bot merged commit bb1e128 into master Nov 17, 2020
@dotnet-maestro dotnet-maestro bot deleted the darc-master-4cce5096-36fd-4b94-ba12-5d198a821a27 branch November 17, 2020 06:56
@mangod9
Copy link
Member

mangod9 commented Nov 17, 2020

great, Thanks everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants