Bug 22062 - Missing 2.0 versions of Mono.C5 and IBM.Data.DB2
Summary: Missing 2.0 versions of Mono.C5 and IBM.Data.DB2
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: General (show other bugs)
Version: master
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-08-13 10:15 UTC by Jo Shields
Modified: 2014-08-25 23:55 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Jo Shields 2014-08-13 10:15:07 UTC
There is only a 4.0-linked version of Mono.C5, which is shipped in multiple places:

directhex@marceline:/tmp/monobadger/lib$ monodis --assembly mono/2.0/Mono.C5.dll 
Assembly Table
Name:          Mono.C5
Hash Algoritm: 0x00008004
Version:       1.1.1.0
Flags:         0x00000001
PublicKey:     BlobPtr (0x00003eab)
	Dump:
0x00000000: 00 24 00 00 04 80 00 00 94 00 00 00 06 02 00 00 
0x00000010: 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 
0x00000020: 21 AB C7 72 C6 A1 B2 5B 4C 79 AF 77 AF 9D D5 E7 
0x00000030: CB 46 B9 67 90 2B EB 1D 01 38 65 95 33 75 62 3B 
0x00000040: 96 B6 9A 11 E3 92 13 1F F8 07 2E 26 F4 42 3B E8 
0x00000050: 51 66 E5 E4 BD FD 84 73 AD 8E FD A1 B5 8B 2A 9F 
0x00000060: 30 B2 F7 A3 6D BD A0 E7 53 6D A4 63 88 17 8F C4 
0x00000070: DF E7 05 5C F8 49 06 56 F5 79 FB C8 23 84 ED 2A 
0x00000080: 6A 77 EF 4C 95 9A 24 4D 59 88 81 24 ED DC 1C 4A 
0x00000090: D9 45 57 28 5A CC 5D EF 4E 09 3F B3 C5 E8 69 F0 
Culture:       

directhex@marceline:/tmp/monobadger/lib$ monodis --assemblyref mono/2.0/Mono.C5.dll 
AssemblyRef Table
1: Version=4.0.0.0
	Name=mscorlib
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 

directhex@marceline:/tmp/monobadger/lib$ monodis --assembly mono/4.5/Mono.C5.dll 
Assembly Table
Name:          Mono.C5
Hash Algoritm: 0x00008004
Version:       1.1.1.0
Flags:         0x00000001
PublicKey:     BlobPtr (0x00003eab)
	Dump:
0x00000000: 00 24 00 00 04 80 00 00 94 00 00 00 06 02 00 00 
0x00000010: 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 
0x00000020: 21 AB C7 72 C6 A1 B2 5B 4C 79 AF 77 AF 9D D5 E7 
0x00000030: CB 46 B9 67 90 2B EB 1D 01 38 65 95 33 75 62 3B 
0x00000040: 96 B6 9A 11 E3 92 13 1F F8 07 2E 26 F4 42 3B E8 
0x00000050: 51 66 E5 E4 BD FD 84 73 AD 8E FD A1 B5 8B 2A 9F 
0x00000060: 30 B2 F7 A3 6D BD A0 E7 53 6D A4 63 88 17 8F C4 
0x00000070: DF E7 05 5C F8 49 06 56 F5 79 FB C8 23 84 ED 2A 
0x00000080: 6A 77 EF 4C 95 9A 24 4D 59 88 81 24 ED DC 1C 4A 
0x00000090: D9 45 57 28 5A CC 5D EF 4E 09 3F B3 C5 E8 69 F0 
Culture:       

directhex@marceline:/tmp/monobadger/lib$ monodis --assemblyref mono/4.5/Mono.C5.dll 
AssemblyRef Table
1: Version=4.0.0.0
	Name=mscorlib
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 


The same goes for IBM.Data.DB2:

directhex@marceline:/tmp/monobadger/lib$ monodis --assembly mono/2.0/IBM.Data.DB2.dll 
Assembly Table
Name:          IBM.Data.DB2
Hash Algoritm: 0x00008004
Version:       1.0.0.0
Flags:         0x00000001
PublicKey:     BlobPtr (0x00000d7f)
	Dump:
0x00000000: 00 24 00 00 04 80 00 00 94 00 00 00 06 02 00 00 
0x00000010: 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 
0x00000020: B7 C4 E6 63 5C 21 31 E5 D4 08 B2 6D B1 ED 18 28 
0x00000030: FD 73 F3 86 A6 BE A9 72 F5 84 FE 8F 72 6C F3 53 
0x00000040: F3 0C 7F 34 33 35 AF 4B 1F E6 F5 F7 08 23 D8 45 
0x00000050: E2 E5 51 B4 20 38 E9 C7 1D D6 74 E2 7E 5E E1 CA 
0x00000060: B6 DD 88 E4 D9 D1 4A 8A 18 82 53 B2 95 7A 2A F1 
0x00000070: 42 17 6D F5 95 99 EB 11 7E 66 64 80 31 08 62 97 
0x00000080: EE 5D 65 77 B4 BD B1 C3 43 B2 A6 A4 09 D6 A2 BE 
0x00000090: 8F 42 52 ED EF E4 75 F1 BB 8A CF 90 DF 57 38 B4 
Culture:       

directhex@marceline:/tmp/monobadger/lib$ monodis --assemblyref mono/2.0/IBM.Data.DB2.dll 
AssemblyRef Table
1: Version=4.0.0.0
	Name=mscorlib
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
2: Version=4.0.0.0
	Name=System.Data
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
3: Version=4.0.0.0
	Name=System
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 

directhex@marceline:/tmp/monobadger/lib$ monodis --assembly mono/4.5/IBM.Data.DB2.dll 
Assembly Table
Name:          IBM.Data.DB2
Hash Algoritm: 0x00008004
Version:       1.0.0.0
Flags:         0x00000001
PublicKey:     BlobPtr (0x00000d7f)
	Dump:
0x00000000: 00 24 00 00 04 80 00 00 94 00 00 00 06 02 00 00 
0x00000010: 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 
0x00000020: B7 C4 E6 63 5C 21 31 E5 D4 08 B2 6D B1 ED 18 28 
0x00000030: FD 73 F3 86 A6 BE A9 72 F5 84 FE 8F 72 6C F3 53 
0x00000040: F3 0C 7F 34 33 35 AF 4B 1F E6 F5 F7 08 23 D8 45 
0x00000050: E2 E5 51 B4 20 38 E9 C7 1D D6 74 E2 7E 5E E1 CA 
0x00000060: B6 DD 88 E4 D9 D1 4A 8A 18 82 53 B2 95 7A 2A F1 
0x00000070: 42 17 6D F5 95 99 EB 11 7E 66 64 80 31 08 62 97 
0x00000080: EE 5D 65 77 B4 BD B1 C3 43 B2 A6 A4 09 D6 A2 BE 
0x00000090: 8F 42 52 ED EF E4 75 F1 BB 8A CF 90 DF 57 38 B4 
Culture:       

directhex@marceline:/tmp/monobadger/lib$ monodis --assemblyref mono/4.5/IBM.Data.DB2.dll 
AssemblyRef Table
1: Version=4.0.0.0
	Name=mscorlib
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
2: Version=4.0.0.0
	Name=System.Data
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
3: Version=4.0.0.0
	Name=System
	Flags=0x00000000
	Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 

Due to the way our build system works, it is not possible to have multiple assemblies with the same version number linked against multiple versions of mscorlib - "make install" will always squash the 2.0 version with the 4.5 version, as the canonical version of the library is whatever's in the GAC (and if the assembly versions are the same, 1.1.1.0-built-with-2.0 will be replaced by 1.1.1.0-built-with-4.5)

There's no obviously good answer to this - apps linked against either library expect the version number they already have. However, the current behaviour is definitely wrong - it means any 2.0 apps linked against those libs will fail to run, due to trying to pull a 4.5 lib into a 2.0 process. We should either build 4.5-only and not ship either lib in 2.0/, or build 2.0-only and not ship either lib in 4.5/
Comment 1 Rodrigo Kumpera 2014-08-25 23:55:08 UTC
We should be killing 2.0, that's the easy solution.

Note You need to log in before you can comment on or make changes to this bug.