Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Revert Linq Version change 4.1.2.0 → 4.2.0.0 *no merge*#14479

Closed
JonHanna wants to merge 1 commit intodotnet:masterfrom
JonHanna:revert_linq_version_bump
Closed

Revert Linq Version change 4.1.2.0 → 4.2.0.0 *no merge*#14479
JonHanna wants to merge 1 commit intodotnet:masterfrom
JonHanna:revert_linq_version_bump

Conversation

@JonHanna
Copy link
Copy Markdown
Contributor

This is failing for me locally, but a comment by @ericstj leads me to suspect maybe that is to be expected. It certainly shouldn't be merged until CI is definitely cleared though.

Comment thread src/System.Linq/ref/System.Linq.csproj Outdated
<PropertyGroup>
<OutputType>Library</OutputType>
<AssemblyVersion>4.2.0.0</AssemblyVersion>
<AssemblyVersion>4.1.2.0</AssemblyVersion>
Copy link
Copy Markdown
Contributor

@justinvp justinvp Dec 13, 2016

Choose a reason for hiding this comment

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

This line was added in #13726. Maybe removing will fix the failures?

Comment thread src/System.Linq/src/System.Linq.csproj Outdated
<ProjectGuid>{CA488507-3B6E-4494-B7BE-7B4EEEB2C4D1}</ProjectGuid>
<AssemblyName>System.Linq</AssemblyName>
<AssemblyVersion>4.2.0.0</AssemblyVersion>
<AssemblyVersion>4.1.2.0</AssemblyVersion>
Copy link
Copy Markdown
Contributor

@justinvp justinvp Dec 13, 2016

Choose a reason for hiding this comment

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

This line was also added in #13726. Maybe removing will fix the failure?

@justinvp
Copy link
Copy Markdown
Contributor

I'm guessing pkg/Microsoft.Private.PackageBaseline/packageIndex.json needs to be changed back too.

@JonHanna JonHanna force-pushed the revert_linq_version_bump branch from 0fcbc4a to 00b5c45 Compare December 13, 2016 21:04
@JonHanna
Copy link
Copy Markdown
Contributor Author

It did.

I can build locally if I change the reference in System.Linq.Tets.csproj from referencing ..\pkg\System.Linq.pkgproj to referencing ..\src\System.Linq.csproj.

What further implications there?

@justinvp
Copy link
Copy Markdown
Contributor

Have you tried reverting the change to packageIndex.json? I didn't see it in the diff here.

https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.Private.PackageBaseline/packageIndex.json#L1607

@JonHanna JonHanna force-pushed the revert_linq_version_bump branch from 00b5c45 to 0cb0dfb Compare December 13, 2016 21:46
@JonHanna
Copy link
Copy Markdown
Contributor Author

Oh for goodness sake. I did, but then committed from too deep a directory and it didn't get included 😊

@JonHanna
Copy link
Copy Markdown
Contributor Author

It would seem some change to layout/Microsoft.Private.CoreFx.NETCoreApp/Microsoft.Private.CoreFx.NETCoreApp.pkgproj or rather something(s) it pulls in needs to be changed.

@ericstj ?

@ericstj
Copy link
Copy Markdown
Member

ericstj commented Dec 13, 2016

None of these are related to the index.

D:\j\workspace\windows_nt_de---4526f5ff\layout\Microsoft.Private.CoreFx.NETCoreApp\Microsoft.Private.CoreFx.NETCoreApp.pkgproj(63,5): error : Assembly 'System.Linq.Expressions' has insufficient version for dependency 'System.Linq' : 4.1.2.0 < 4.2.0.0.
D:\j\workspace\windows_nt_de---4526f5ff\layout\Microsoft.Private.CoreFx.NETCoreApp\Microsoft.Private.CoreFx.NETCoreApp.pkgproj(63,5): error : Assembly 'Microsoft.CSharp' has insufficient version for dependency 'System.Linq' : 4.1.2.0 < 4.2.0.0.
D:\j\workspace\windows_nt_de---4526f5ff\layout\Microsoft.Private.CoreFx.NETCoreApp\Microsoft.Private.CoreFx.NETCoreApp.pkgproj(63,5): error : Assembly 'System.Security.Cryptography.Encoding' has insufficient version for dependency 'System.Linq' : 4.1.2.0 < 4.2.0.0.
D:\j\workspace\windows_nt_de---4526f5ff\layout\Microsoft.Private.CoreFx.NETCoreApp\Microsoft.Private.CoreFx.NETCoreApp.pkgproj(63,5): error : Assembly 'System.ComponentModel.TypeConverter' has insufficient version for dependency 'System.Linq' : 4.1.2.0 < 4.2.0.0.

These are all problematic. Those errors are occurring when I do a closure walk of the final output.

These are ref-def mismatches in the final package set that will cause runtime issues. They're happening because each of these libraries is building against the old packages.

We could fix them all by adding p2p references but that is going to be painful.

I'm tempted to leave this as it is. If we want to make this change that will be much easier once dev/eng work is done.

@JonHanna JonHanna closed this Dec 13, 2016
@karelz karelz modified the milestone: 2.0.0 Dec 14, 2016
@JonHanna JonHanna deleted the revert_linq_version_bump branch December 14, 2016 02:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants