Your message dated Mon, 26 Mar 2018 16:50:58 +0000 with message-id <[email protected]> and subject line Bug#893860: Removed package(s) from unstable has caused the Debian Bug report #841882, regarding monodevelop: TargetFramework not properly generated for Mono/.NET 4.0 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 841882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841882 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: monodevelop Version: 5.10.0.871-2 Severity: important When building a project and targeting Mono/.NET 4.0 an assemlyinfo file is automatically generated in the obj folder: .NETFramework\,Version\=v4.5.AssemblyAttribute.cs ------------------------------------------------ The content of this file is: // <autogenerated /> [assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.5", FrameworkDisplayName = "")] ------------------------------------------------ When targeting Mono/.NET 4.0 the file should be named .NETFramework\,Version\=v4.0.AssemblyAttribute.cs ----------------------------------------------- And the content of this file should be: // <autogenerated /> [assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.0", FrameworkDisplayName = "")] ------------------------------------------------ as per: https://msdn.microsoft.com/en- us/library/system.runtime.versioning.targetframeworkattribute(v=vs.110).aspx I don't know if that alone would be enough. I was writing some test code and targeting Mono/.Net 4.0 (I could target 4.5) -- the fact that there are two seperate options indicates, to me, that they are building against different runtime versions. Under mono (and wine when targeting v4.0/v4.5) the code runs correctly. However that some code (compiled aginst v4.0) will not execute on any system where .Net 4.5 cannot be installed. What happended is that (as with my code) the code (on Windows XP) would throw missing method exceptions for Marshal.SizeOf, Marshal.StructureToPtr, etc -- because instead of targeting v4.0 is was actually built against v4.5. I'm not sure if this was a bug, or intended behavior. -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (1001, 'testing-debug'), (1001, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages monodevelop depends on: ii gnome-icon-theme 3.12.0-2 ii gnome-terminal [x-terminal-emulator] 3.22.0-3 ii libc6 2.24-3 ii libcairo2 1.14.6-1+b1 ii libfontconfig1 2.11.0-6.7 ii libgconf2.0-cil 2.24.2-4 ii libglade2.0-cil 2.12.10-6 ii libglib2.0-0 2.50.1-1 ii libglib2.0-cil 2.12.10-6 ii libgnome-vfs2.0-cil 2.24.2-4 ii libgnome2.24-cil 2.24.2-4 ii libgtk2.0-0 2.24.31-1 ii libgtk2.0-cil 2.12.10-6 ii libgtkspell0 2.0.16-1.1 ii libmono-cairo4.0-cil 4.2.1.102+dfsg2-8 ii libmono-corlib4.5-cil 4.2.1.102+dfsg2-8 ii libmono-microsoft-build-engine4.0-cil 4.2.1.102+dfsg2-8 ii libmono-microsoft-build-framework4.0-cil 4.2.1.102+dfsg2-8 ii libmono-microsoft-build-utilities-v4.0-4.0-cil 4.2.1.102+dfsg2-8 ii libmono-microsoft-csharp4.0-cil 4.2.1.102+dfsg2-8 ii libmono-posix4.0-cil 4.2.1.102+dfsg2-8 ii libmono-sharpzip4.84-cil 4.2.1.102+dfsg2-8 ii libmono-system-componentmodel-dataannotations4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-configuration4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-core4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-data-services-client4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-data4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-design4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-drawing4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-numerics4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-runtime-serialization4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-runtime4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-security4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-servicemodel4.0a-cil 4.2.1.102+dfsg2-8 ii libmono-system-web-mvc3.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-web-razor2.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-web-services4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-web-webpages-razor2.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-web4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-windows-forms4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-xaml4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-xml-linq4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system-xml4.0-cil 4.2.1.102+dfsg2-8 ii libmono-system4.0-cil 4.2.1.102+dfsg2-8 ii libmono-windowsbase4.0-cil 4.2.1.102+dfsg2-8 ii libpango-1.0-0 1.40.3-2 ii libpangocairo-1.0-0 1.40.3-2 ii libwebkitgtk-1.0-0 2.4.11-3 ii mate-terminal [x-terminal-emulator] 1.16.1-1 ii mono-runtime 4.2.1.102+dfsg2-8 ii mono-runtime-sgen 4.2.1.102+dfsg2-8 ii mono-xbuild 4.2.1.102+dfsg2-8 ii monodoc-base 4.2.1.102+dfsg2-8 ii monodoc-manual 4.2.1.102+dfsg2-8 ii pkg-config 0.29-4 ii xterm [x-terminal-emulator] 327-1 Versions of packages monodevelop recommends: ii libglade2.0-cil-dev 2.12.10-6 ii libgtk2.0-cil-dev 2.12.10-6 ii mono-devel 4.2.1.102+dfsg2-8 Versions of packages monodevelop suggests: pn exuberant-ctags <none> ii gcc 4:6.1.1-1 ii gettext 0.19.8.1-1 ii make 4.1-9 ii mono-vbnc 4.0.1-1 ii mono-xsp 4.2-2 ii mono-xsp4 4.2-2 ii monodevelop-database 5.10.0.871+dfsg-1 pn monodevelop-debugger-gdb <none> ii monodevelop-nunit 5.10.0.871-2 ii monodevelop-versioncontrol 5.10.0.871-2 ii monodoc-browser 4.2-1 ii zip 3.0-11 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 5.10.0.871-2+rm Dear submitter, as the package monodevelop has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/893860 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
