Package: mono-xbuild Version: 3.0.6+dfsg2-10 Severity: serious Hi there,
I tried using xbuild in my fresh and shiny unstable chroot. This failed horribly: | $ xbuild | Missing method .ctor in assembly /usr/lib/mono/gac/Microsoft.Build.Engine/4.0.0.0__b03f5f7f11d50a3a/Microsoft.Build.Engine.dll, type System.Runtime.CompilerServices.ExtensionAttribute | Can't find custom attr constructor image: /usr/lib/mono/gac/Microsoft.Build.Engine/4.0.0.0__b03f5f7f11d50a3a/Microsoft.Build.Engine.dll mtoken: 0x0a000297 | Missing method .ctor in assembly /usr/lib/mono/gac/System.Core/4.0.0.0__b77a5c561934e089/System.Core.dll, type System.Runtime.CompilerServices.ExtensionAttribute | Can't find custom attr constructor image: /usr/lib/mono/gac/System.Core/4.0.0.0__b77a5c561934e089/System.Core.dll mtoken: 0x0a0001d8 | | Unhandled Exception: | System.TypeLoadException: Could not load type 'System.Runtime.CompilerServices.ExtensionAttribute' from assembly 'System.Core'. | at Mono.XBuild.CommandLine.Parameters.ParseArguments (System.String[] args) [0x00000] in <filename unknown>:0 | at Mono.XBuild.CommandLine.MainClass.Execute () [0x00000] in <filename unknown> | at Mono.XBuild.CommandLine.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0 As this always occurs, the package mono-xbuild is largely useless after installation (hence the severity of the bug). Some digging revealed that while mono-xbuild depends on libmono-corlib4.5-cil, the way things are currently set up, CIL 4.0 is picked up. A workaround to this problem is to explicitly set MONO_PATH=/usr/lib/mono/4.5/ when invoking xbuild. Of course, that's not a good permanent solution... Anyway, thanks for doing all this work: While somewhat unpolished, the packages largely worked and allowed me to port a relatively large F# application to Linux in a few hours. Marc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
