kzwkt / winetricks

Automatically exported from code.google.com/p/winetricks
0 stars 0 forks source link

dotnet35sp1 install fails because of a confict #416

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
installing dotnet35sp1 eventually fails with:

"error: dotnet20sp2 conflicts with dotnet20sp1, which is already installed."

dotnet20sp1 is pulled in by previours dotnet versions, which are being 
installed when trying to install dotnet35sp1, therefore dotnet35sp1 is 
uninstallable.

Tested with clean win32 wineprefix & latest winetricks script (downloaded from 
svn @ 22.03.2014).

Original issue reported on code.google.com by spitfire...@gmail.com on 22 Mar 2014 at 3:44

GoogleCodeExporter commented 9 years ago
Please attach a log with winetricks -v

It keeps failing for me in dotnet35, so I can't reproduce it.

Original comment by austinenglish@gmail.com on 22 Mar 2014 at 7:25

GoogleCodeExporter commented 9 years ago
Log attached. I've suppresed wine debug to make it more readable, let me know 
if you need it with wine debug.

On a side note, I've just checked with winetricks 20130629 (shipped with Mint 
16) and it installs dotnet35sp1 fine (with some warnings from the installers, 
but still).

Original comment by spitfire...@gmail.com on 22 Mar 2014 at 7:59

Attachments:

GoogleCodeExporter commented 9 years ago
I've just noticed that in my last comment I ran "./winetricks -v dotnet35sp1", 
so it complains about msxml3 conflict (so, yet another conflict bug I guess) 
not dotnetsp20sp2 as I first reported.

I re-run the script with "./winetricks -v msxml3 dotnet35sp1", identical with 
my first post, log attached.

Original comment by spitfire...@gmail.com on 22 Mar 2014 at 8:13

Attachments:

GoogleCodeExporter commented 9 years ago
I can reproduce it now, looking..

Original comment by austinenglish@gmail.com on 22 Mar 2014 at 11:20

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1153.

Original comment by austinenglish@gmail.com on 23 Mar 2014 at 11:23

GoogleCodeExporter commented 9 years ago
The msxml3 issue was fixed by r1153 (nesting conflicts was broken, which was 
masked by general .net breakage). dotnet35sp1 is still broken, my too 
aggressive conflicts, I'm looking at it now.

Original comment by austinenglish@gmail.com on 23 Mar 2014 at 11:48

GoogleCodeExporter commented 9 years ago
r1154 fixes this semi-properly.

I say semi-properly, because now:
winetricks dotnet20sp1 dotnet20sp2

is now allowed, but broken (dotnet20 dotnet20sp1 may also break, but works for 
me, at least now). That's a separate issue (and likely a wine bug).

Original comment by austinenglish@gmail.com on 24 Mar 2014 at 12:37