Your message dated Mon, 01 Apr 2013 09:32:58 +0000 with message-id <e1umb6o-0005gq...@franck.debian.org> and subject line Bug#703332: fixed in mummy 1.0.3-2 has caused the Debian Bug report #703332, regarding If they are API compatible you MUST generate and install a GAC policy file! 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 ow...@bugs.debian.org immediately.) -- 703332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libactiviz.net-cil ---------- Forwarded message ---------- From: Jo Shields <direct...@apebox.org> Date: Mon, Mar 18, 2013 at 4:20 PM Subject: Re: Invalid dependencies (Re: Unhandled Exception: Mono.CSharp.InternalErrorException) To: Mathieu Malaterre <ma...@debian.org> Cc: debian-...@lists.debian.org On Mon, 2013-03-18 at 16:08 +0100, Mathieu Malaterre wrote: > On Mon, Mar 18, 2013 at 3:49 PM, Jo Shields <direct...@apebox.org> wrote: > > On Mon, 2013-03-18 at 15:34 +0100, Mathieu Malaterre wrote: > >> Using monodis, I finally found out the issue. libactiviz.net-cil > >> 1:1.0~git20111214-1 on amd64 is build against an older mummy release. > >> Therefore we have: > >> > >> $ monodis --assemblyref /usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > >> [...] > >> 2: Version=1.0.2.599 > >> Name=Kitware.mummy.Runtime > >> Flags=0x00000000 > >> Public Key: > >> > >> > >> While, if one recompiles+install, we get: > >> > >> $ monodis --assemblyref /usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > >> [...] > >> 2: Version=1.0.3.599 > >> Name=Kitware.mummy.Runtime > >> Flags=0x00000000 > >> Public Key: > >> > >> > >> So the short solution is to request a binNMU of libactiviz.net-cil. > >> But the long solution would be to have proper dependencies checking. > >> > >> Could some C# gurus let me know if there is anything missing in my > >> activiz.net and/or mummy package to generate proper dependencies (and > >> therefore have a btter long term solution) ? > >> > >> Thanks *very* much ! > > > > The first question is "are the two versions ABI-compatible?" - if the > > ABI hasn't actually been broken (i.e. there are no removed methods or > > properties) then you can include a GAC policy file which maps all > > applications looking for the old ABI to the new ABI. For example, apps > > with a moduleref for Mono.Addins 0.2.0.0, 0.3.0.0, 0.4.0.0, or 0.5.0.0 > > will still work with our 0.6.0.0 packages, thanks to policy files. The > > command "mono-api-check" can be used to compare two assemblies to see if > > their ABIs are compatible or not; the man page for dh_cligacpolicy shows > > how to write a cligacpolicy file to do policy mapping, if appropriate. > > > > $ mono-api-check ./sid/usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > ./loc/usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > Error: mono-api-info on ./sid/usr/lib/cli/ActiViz.NET/Kitware.VTK.dll failed! > $ man mono-api-check > No manual entry for mono-api-check > See 'man 7 undocumented' for help when manual pages are not available. > > Same goes with .deb package: > > > $ mono-api-check ./sid/libactiviz.net-cil_1.0~git20111214-1_amd64.deb > ./libactiviz.net-cil_1.0~git20111214-1_amd64.deb > Library: /usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > Error: mono-api-info on > /tmp/mono-api-check-1192-7700/usr/lib/cli/ActiViz.NET/Kitware.VTK.dll > failed! > > Any extra information on how to use this tool also very appreciated ! $ mono-api-check a/usr/lib/cli/Kitware.mummy.Runtime-1.0/Kitware.mummy.Runtime.dll b/usr/lib/cli/Kitware.mummy.Runtime-1.0/Kitware.mummy.Runtime.dll CLI API Check Assembly Name: Kitware.mummy.Runtime Missing Interfaces: 0 Additional Interfaces: 0 The assembly versions do NOT MATCH! If they are API compatible you MUST generate and install a GAC policy file! Seems compatible to me! This is a pretty basic upstream error - the assembly version should be treated as an ABI version declaration, not something to bump ad hoc, for precisely the reasons you've run into. There is no difference between the version 1.0.2 build revision 599 ABI, and version 1.0.3 build revision 599 ABI which would require bumping this ABI version. Using GAC policy is a simple way to work around this kind of stupidity (MySQL's bindings do the same)
--- End Message ---
--- Begin Message ---Source: mummy Source-Version: 1.0.3-2 We believe that the bug you reported is fixed in the latest version of mummy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 703...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre <ma...@debian.org> (supplier of updated mummy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Mon, 01 Apr 2013 09:33:20 +0200 Source: mummy Binary: mummy libkitware-mummy-runtime1.0-cil mummy-doc Architecture: source amd64 all Version: 1.0.3-2 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team <debian-med-packag...@lists.alioth.debian.org> Changed-By: Mathieu Malaterre <ma...@debian.org> Description: libkitware-mummy-runtime1.0-cil - Mummy CLI bindings mummy - command line executable that generates C# wrappers from gccxml ou mummy-doc - mummy class reference documentation Closes: 703332 Changes: mummy (1.0.3-2) unstable; urgency=low . * Fix ABI version. Closes: #703332 + debian/libkitware-mummy-runtime1.0-cil.cligacpolicy Checksums-Sha1: ad638382fb1b7d7f8843162fa9382fc6e82de42a 2204 mummy_1.0.3-2.dsc df2d54fa1a4fa78006f56f14f5c31b40e158e6e2 7733 mummy_1.0.3-2.debian.tar.gz afc0be9ba2c2b885b805ed6074ec791f86d8130e 315668 mummy_1.0.3-2_amd64.deb 3afb737e3e11c31319efc965d39d7fdde79c3cb6 28236 libkitware-mummy-runtime1.0-cil_1.0.3-2_amd64.deb 8aff6eb586860321b87d65f944025331e3161d37 970244 mummy-doc_1.0.3-2_all.deb Checksums-Sha256: ad3c59d6b3d25c5ed3028961fb9c012090c1b9bb99eb21478031c3b9c8283c73 2204 mummy_1.0.3-2.dsc 99b989c5e2239a921ae2b1d641c1c7f7f21ebe87b9e0d649dd447469377621da 7733 mummy_1.0.3-2.debian.tar.gz a5f94a4026fc4244c8392fc586211ad7175174f4c72ec4ae956f74bbe7684901 315668 mummy_1.0.3-2_amd64.deb 5631e07d580212741afbefb5ccc1dcce572fe347a515483e24a429cf90deeb8f 28236 libkitware-mummy-runtime1.0-cil_1.0.3-2_amd64.deb f0cde94d6f89979ae849a33d0b66cb1c14a183a2559a567193d7de378da7e11c 970244 mummy-doc_1.0.3-2_all.deb Files: c6f68db96b97663b82d94309ffab5d6a 2204 devel extra mummy_1.0.3-2.dsc eb782295b0c5f50bc4c710fa5d1d8fab 7733 devel extra mummy_1.0.3-2.debian.tar.gz 0b6b2fe13945c0c916c4a3bc9a477401 315668 devel extra mummy_1.0.3-2_amd64.deb 2e551a8d54042b0d81e24bfabfea864d 28236 cli-mono extra libkitware-mummy-runtime1.0-cil_1.0.3-2_amd64.deb 0fee1124007d3818c437b9fe0613c247 970244 doc extra mummy-doc_1.0.3-2_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJRWUomAAoJEAFx4YKK4JNFesQP/itDJJkwCBIGsEFtcl50WaSq XnaLNGcXddN/nGNqnJhPdKRgPhdu6lsMGUQXZL3HJUGjIHMW4R25S8FShbz/b5Pf Vo1IzQRaps//C1hvcSB85T9pj65oXU4K70jUUJjjrItbpKPaRIR7V4c17xZI0ygq reIUjucX9hMfLMbX1H8BTVw5V77GIEKADbnC0Q/Uz2Rp8YZypt8vgUEqTza3evHU iriU4vsdtqTHuzhtulM0BkLXG94cNS8Z9wZuezybb/CGO9f6U65HYcdr0WVJG78G o4rmVgk8snFc2ndeJb/lbOzgmeHDd/0w0AzUBODp+FMlFMd69qLLqH/1E1/LKBgp +lBFEHGjbo/tQmAs+utGuud3XWH/DDbY0v3WpMtRbA05+ueWN+SzFviwDdwhmnP/ SzkY1J1kvRnFNJQhyHN7MV9CaevpQwvUqVd+OZKDKXgau6bZ9nAd+rUrWEHj+Gt+ z5b9TkM/rbSuVjcnp85vCEOJbs/HN8+aYBH/ezmA9e6GWUW8bQreQ248LYDWVBI1 bISA52+4RR3UK5vskgt0wAzlvb/06CAqDviGSqLs93hZkqMR+PEtWGRhbubaz532 qGQVVo+KIedX8ox8kJudMa9e7h2uMneJaU1f1OmmEozbR6joFd24ssxk1BarVT5g R+LZXSf1CHaSl8ZNShOg =19sy -----END PGP SIGNATURE-----
--- End Message ---
