[Pkg-mono-devel] E: installing Assembly /usr/lib/cli/Kitware.mummy.Runtime-1.0/Kitware.mummy.Runtime.dll failed
Mathieu Malaterre
mathieu.malaterre at gmail.com
Thu Feb 24 14:21:43 UTC 2011
On Sat, Feb 19, 2011 at 11:55 AM, Jo Shields <directhex at apebox.org> wrote:
> It's not a problem - it's a reasonably common warning when putting CLI
> stuff and C stuff in the same package without using a dllmap. You'll see
> similar errors in the build logs for things like Banshee.
>
> There are a few other packaging errors and oddities though.
>
> Firstly, you identify libmummy-1.0-cil as " CLI bindings to the Mummy
> library" - but the package isn't depending on anything identifying
> itself as "the Mummy library", so it's not really a binding.
>
> Secondly, if it's a lib that should be used for development (i.e. a
> binding), then there should be a .pc file in a -cil-dev package. If it's
> not for that, then it's not clear to me how one would "use" the package.
>
> Thirdly, package install locations should reflect the assembly name (and
> not contain a spurious dash, much like a C soname), so
> Kitware.mummy.Runtime.dll lives
> in /usr/lib/cli/Kitware.mummy.Runtime-1.0/ - assuming it's a GAC
> library, which leads on to point 4:
>
> Fourthly, if a lib is a GAC lib, it should be in a version-numbered
> package and go in /usr/lib/cli (in this case,
> libkitware-mummy-runtime1.0-cil) - and include a .installcligac file to
> specify that the lib should go into the GAC where apps can consume it.
> In this case, the lib isn't installing to the GAC, so I'm not sure if it
> should follow the GAC rules or is expected to go into the GAC - if not,
> the package name should not include a version number, the install
> location should just be in /usr/lib/ not /usr/lib/cli, and a valid
> pkg-config file becomes all the more important
Thanks a lot for commenting on my draft-package !
I believe I have taken care of all your remarks above. Namely:
- I do not provide .pc files since this is a cmake package, I only
ships *.cmake file to 'use' the package. This has been added to
README.Debian for clarification
- I fixed the naming convention as per your recommendations
- I added a libkitware-mummy-runtime1.0-cil.installcligac to finish the install
However it seems I am still missing something when installing it, I get:
Processing triggers for man-db ...
Setting up libkitware-mummy-runtime1.0-cil (1.0.2-1) ...
* Installing 1 assembly from libkitware-mummy-runtime1.0-cil into Mono
E: installing Assembly
/usr/lib/cli/Kitware.mummy.Runtime-1.0/Kitware.mummy.Runtime.dll
failed
E: Installation of libkitware-mummy-runtime1.0-cil with
/usr/share/cli-common/runtimes.d/mono failed
dpkg: error processing libkitware-mummy-runtime1.0-cil (--configure):
subprocess installed post-installation script returned error exit status 9
configured to not write apport reports
I have pushed my new package to mentors, it should appear in a bit:
http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;package=mummy
Thanks again,
--
Mathieu
More information about the Pkg-mono-devel
mailing list