[Pkg-mono-devel] Help on packaging galaxium

[Mirco Bauer]

On Thu, 2008-06-19 at 10:03 +0200, David Paleino wrote:
> Hi all,
> I'm packaging galaxium (ITP #476959), a CLI IM messenger (currently supports
> only MSN, but previously it also supported IRC and other protocols -- which
> were disabled because too "unstable").
> You can have a look at pkg-cli-apps/packages/galaxium.
> It successfully compiles, but when I run dh_makeclilibs and dh_clideps, I get:
> 
> > dh_makeclilibs: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)!
> 
> This isn't true, as you can see in debian/control (it *is* in Build-Depends!)

Thats a false-positive (the check of dh_*cli* are very stupid) :)

> 
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/Galaxium.Protocol.dll has no valid signature, ignoring
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/Galaxium.Client.dll has no valid signature, ignoring
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/ProxySocket.dll has no valid signature, ignoring
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/libmimic-sharp.dll has no valid signature, ignoring
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/Galaxium.GStreamer.dll has no valid signature, ignoring
> > dh_makeclilibs: debian/galaxium/usr/lib/galaxium/Galaxium.WebKit.dll has no valid signature, ignoring
> > [..]
> 
> I don't really know how to fix this.
> Should I contact upstream? Should I sign those assemblies myself? If yes,
> how? (I didn't find much in the CLI policy...)

I doubt those are public libraries that should be used by other
applications, so just ignore it like dh_makecllibs does. You probably
should not call dh_makeclilibs at all....

> 
> > dh_clideps
> > dh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)!
> > dh_clideps: Warning: Could not resolve moduleref: libmimic for: libmimic-sharp.dll!
> > dh_clideps: Warning: Could not resolve moduleref: libgalaxium for: Galaxium.GStreamer.dll!
> > dh_clideps: Warning: Could not resolve moduleref: Iphlpapi.dll for: agsXMPP.dll!
> > dh_clideps: Warning: Could not resolve moduleref: Kernel32.dll for: agsXMPP.dll!
> > [..]
> 
> Again as before: what to do here?

There you need some DLLmap love, check the policy chapter about DLL
maps.

> 
> 
> Also: the upstream source tarball ships some .dll's:
> 
> $ ls -1 dlls/
> agsXMPP.dll
> Dependencies.txt
> Makefile.am
> Mono.Nat.dll
> Mono.Nat.license.txt
> ProxySocket.dll
> ProxySocket.license.txt
> $
> 
> Debian (and me as well) is usually against using "embedded copies" of code --
> I've contacted upstream to have the original sources for those assemblies.
> Obviously, I will package all those dlls as separate packages (if they aren't
> already there).

Debian can live with embedded copies of _source_ _code_ but not
binaries, they violate the DFSG as you can not change them, nor can
debian provide security for those. They must be removed from the tarball
and be replaced with either source or debian library packages.

And be sure to check the licensed of those libraries, I found some
licensing issues lately in the Mono application area ;)

> 
> Thanks for any help,
> David
> 

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey at meebey.net  http://www.meebey.net/
PEAR Developer    meebey at php.net     http://pear.php.net/
Debian Developer  meebey at debian.org  http://www.debian.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20080619/95fc8f8d/attachment.pgp