Your message dated Thu, 11 Apr 2013 11:02:52 +0000
with message-id <[email protected]>
and subject line Bug#703332: fixed in mummy 1.0.3-3
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 [email protected]
immediately.)
--
703332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703332
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libactiviz.net-cil
---------- Forwarded message ----------
From: Jo Shields <[email protected]>
Date: Mon, Mar 18, 2013 at 4:20 PM
Subject: Re: Invalid dependencies (Re: Unhandled Exception:
Mono.CSharp.InternalErrorException)
To: Mathieu Malaterre <[email protected]>
Cc: [email protected]
On Mon, 2013-03-18 at 16:08 +0100, Mathieu Malaterre wrote:
> On Mon, Mar 18, 2013 at 3:49 PM, Jo Shields <[email protected]> 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-3
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Malaterre <[email protected]> (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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Thu, 11 Apr 2013 09:58:20 +0000
Source: mummy
Binary: mummy libkitware-mummy-runtime1.0-cil mummy-doc
Architecture: source amd64 all
Version: 1.0.3-3
Distribution: wheezy
Urgency: low
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Mathieu Malaterre <[email protected]>
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-3) wheezy; urgency=low
.
* Fix ABI version. Closes: #703332
Checksums-Sha1:
f5a5d7c1984e2e97cc01f623c5cdc6ef111d4ada 2204 mummy_1.0.3-3.dsc
5cdc2246d463f85928e46f66a1d8d62f03fab6c5 7735 mummy_1.0.3-3.debian.tar.gz
6476cfc890808a2cdd98bfdbaa2a740469408dfd 315702 mummy_1.0.3-3_amd64.deb
3b7694421e0c9bed8bc762bb22ed6e1c5cb2d9a7 28272
libkitware-mummy-runtime1.0-cil_1.0.3-3_amd64.deb
610ef5bac5b94d4a2029a7e009603aebe088b7ca 975914 mummy-doc_1.0.3-3_all.deb
Checksums-Sha256:
43f92f63939d987ce70680400f8531e454b3eec542c21283d44c321780672d61 2204
mummy_1.0.3-3.dsc
6e2fa87437886b2139723b5974b936b98abbdeae0c7d880abf12e47ab269109d 7735
mummy_1.0.3-3.debian.tar.gz
186e07dd8b341dab8ab7f2e5da5c40532fabb354d1e058ec680addfb287afb64 315702
mummy_1.0.3-3_amd64.deb
2c9055924e3183aac051aa0d05427e9bb831067a8647569c1848e10902ba1d77 28272
libkitware-mummy-runtime1.0-cil_1.0.3-3_amd64.deb
ad4167a42c46e18d8481f3dc4b010ca88675e5437355684727c9cdeae7c61697 975914
mummy-doc_1.0.3-3_all.deb
Files:
d021562e5ec7fa66523110318ffdc334 2204 devel extra mummy_1.0.3-3.dsc
ab7d6f6af8e726c8c774d0ff48bc068e 7735 devel extra mummy_1.0.3-3.debian.tar.gz
93742966ce45ec336d7750b0542ccc3f 315702 devel extra mummy_1.0.3-3_amd64.deb
04ebf628420e2951eac3c1e9b971a239 28272 cli-mono extra
libkitware-mummy-runtime1.0-cil_1.0.3-3_amd64.deb
d15575e58e91ebada12abee9e19506ea 975914 doc extra mummy-doc_1.0.3-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJRZpVaAAoJEAFx4YKK4JNFk2UP/jwFbN2mIyF2VC2P2hxyrLFM
DbT822vjK9QmidkXVDPkzCweyJ/4txfbTj9Fru7T7gz1e2Q2iTaBGP7pm+v/+1QQ
6WqKQ2p+yUTeCAySyzVtJgwN17WqyLLu8mLLjWJYFZSGu1MvwA2Ai/fHapxfKcyB
IlJBUMYBqkayLzDi8dhe+rkBsqG97jdkDp2QJ8jXzofSoDgFBYj/7uaXzRt5ZgwM
43VHsuzfwIuLFB/XYcP3aCYZRFHvGE+MreUvQAz0kcShbvD30wxvgi+UZLSYmEWL
zVLFGX/bZVH1fzAkU604GsCxvewArSX5jTUHGqvi8Oi4G2im6sGf5FF4ZAB/MxHH
YpCSIrrwZGVHCLijvTS5r2yle96XCSKCFDfTq9bvTSQyqvHp4DrkKxtPKG+Zr1WQ
Yihuh9xD4BmhfN7srbK2iu14fAeEoavgJ2aC+kOcrqFYBzK2DsY8HaMeMyIcWXwQ
45dC0tHJh+OYRwiR1wNC4henz4UMQhKy2jt5BY5BYDW6uZVCnwAwIMbgIle2bA/G
DZ41csRR7Mb+iDtIIUaujB1pDcPfyPECryvigQ83hB2LTI/d4K0lDYe6Pha9qdgb
CS9EUvIBMSzho4gI1wjXh8We+vuJKsM0jnxFMpE2w+hNNTinrGioeGBh2KUje2Q3
poKtUhup4Wfw8TGprtqE
=9WVS
-----END PGP SIGNATURE-----
--- End Message ---
