[Pkg-giraffe-discuss] lintian update

[Guido Günther]

On Fri, Jun 19, 2015 at 02:35:11PM +0200, Mark Dufour wrote:
> hi all,
> 
> today I moved libzarafaclient.so and  libzarafacontacts.so into libdir/zarafa. after also updating several extended-descriptions, and ignoring the hardening warnings, I'm left with the following list (on our SVN trunk):
> 
> I: zarafa-spooler: conflicts-with-version zarafa (<< 7.3)
> E: libzarafa-soapserver0: extended-description-is-empty
> I: libzarafa-soapserver0: no-symbols-control-file usr/lib/libzarafa_soapserver.so.0.0.0
> E: libzcp-common-service0: extended-description-is-empty
> I: libzcp-common-service0: no-symbols-control-file usr/lib/libzcp_common_service.so.0.0.0
> I: libicalmapi1: extended-description-is-probably-too-short
> I: libicalmapi1: no-symbols-control-file usr/lib/libicalmapi.so.1.0.0
> W: zarafa-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libzarafa_soapclient.so.0.0.0
> W: zarafa-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libzarafa_soapserver.so.0.0.0
> I: libinetmapi1: no-symbols-control-file usr/lib/libinetmapi.so.1.0.0
> W: libzarafa-archiver-core0: extended-description-line-too-long
> I: libzarafa-archiver-core0: extended-description-is-probably-too-short
> I: libzarafa-archiver-core0: no-symbols-control-file usr/lib/libzarafa-archiver-core.so.0.0.0
> I: zarafa-gateway: conflicts-with-version zarafa (<< 7.3)
> W: zarafa-contacts: maintainer-script-ignores-errors postinst
> W: zarafa-contacts: postinst-has-useless-call-to-ldconfig
> E: libzcp-common-ssl0: extended-description-is-empty
> X: libzcp-common-ssl0: shlib-calls-exit usr/lib/libzcp_common_ssl.so.0.0.0
> I: libzcp-common-ssl0: no-symbols-control-file usr/lib/libzcp_common_ssl.so.0.0.0
> I: zarafa-ical: conflicts-with-version zarafa (<< 7.3)
> I: libfreebusy0: extended-description-is-probably-too-short
> I: libfreebusy0: no-symbols-control-file usr/lib/libfreebusy.so.0.0.0
> W: libzarafa-archiver0: extended-description-line-too-long
> I: libzarafa-archiver0: extended-description-is-probably-too-short
> I: libzarafa-archiver0: no-symbols-control-file usr/lib/libzarafa-archiver.so.0.0.0
> W: zarafa: empty-binary-package
> I: zarafa-client: conflicts-with-version zarafa (<< 7.3)
> E: libzarafa-soapclient0: extended-description-is-empty
> I: libzarafa-soapclient0: no-symbols-control-file usr/lib/libzarafa_soapclient.so.0.0.0
> I: zarafa-dev: extended-description-is-probably-too-short
> I: libmapi1: no-symbols-control-file usr/lib/libmapi.so.1.0.0
> I: libzcp-common-util0: spelling-error-in-binary usr/lib/libzcp_common_util.so.0.0.0 Nam Name
> E: libzcp-common-util0: extended-description-is-empty
> I: libzcp-common-util0: no-symbols-control-file usr/lib/libzcp_common_util.so.0.0.0
> I: zarafa-common: description-synopsis-might-not-be-phrased-properly
> I: zarafa-common: extended-description-is-probably-too-short
> I: zarafa-common: conflicts-with-version zarafa (<< 7.3)
> W: zarafa-common: maintainer-script-ignores-errors postinst
> I: zarafa-monitor: conflicts-with-version zarafa (<< 7.3)
> E: libzarafa-server0: extended-description-is-empty
> X: libzarafa-server0: shlib-calls-exit usr/lib/libzarafa_server.so.0.0.0
> I: libzarafa-server0: no-symbols-control-file usr/lib/libzarafa_server.so.0.0.0
> I: zarafa-utils: conflicts-with-version zarafa (<< 7.3)
> I: zarafa-server: conflicts-with-version zarafa (<< 7.3)
> I: zarafa-server: package-contains-empty-directory usr/share/zarafa/userscripts/
> W: zarafa-server: maintainer-script-ignores-errors postinst
> I: php5-mapi: conflicts-with-version zarafa (<< 7.3)
> I: zarafa-dagent: conflicts-with-version zarafa (<< 7.3)
> E: zarafa-lang: extended-description-is-empty
> I: zarafa-lang: conflicts-with-version zarafa (<< 7.3)
> I: zarafa-lang: conflicts-with-version zarafa-client (<< 7.3)
> X: zarafa-lang: package-contains-no-arch-dependent-files
> E: libzarafasync0: extended-description-is-empty
> I: libzarafasync0: no-symbols-control-file usr/lib/libzarafasync.so.0.0.0
> E: libzcp-common-mapi0: extended-description-is-empty
> I: libzcp-common-mapi0: no-symbols-control-file usr/lib/libzcp_common_mapi.so.0.0.0
> 
> we are planning on doing another beta in about two weeks, and I'm confident most of the changes in trunk can still be merged before that. 
> 
> do you guys have any idea how to solve the symbols-related warnings? if we can make these disappear, the hardening stuff is solved, we do something about the conflicts and fill in some more extended descriptions, I guess we could be down to about 10 lines.. most of which seems pretty easy to solve ^^

The versioned conflicts should very likely be Breaks (but only you can
tell if that is sufficient to upgrade from an older version). You only
need conflicts if the packages can't even be unpacked at the same time
on a system. What's the reason for the Conflicts anyway?

Some of the packages that have empty descriptions aren't in our packges
on alioth, did they come out of the library rename?

The symbol files will be helpful for dependency tracking and detecting
ABI preckage in the future, you can simply generate them:

    https://wiki.debian.org/UsingSymbolsFiles

It would certainly be best if Zarafa would start maintaining the symbol
information upstream like we do e.g. in libvirt to have proper ABI
guarantees:

    http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/libvirt_public.syms;h=59d8c122023044ce378fd5f7024ef23c11cd3736;hb=HEAD

Pumping symbol versions will the become as simple as:

   https://anonscm.debian.org/cgit/pkg-libvirt/libvirt.git/commit/?id=5e4d9b7e064ba5ec9219ffa51581547c44f6cbef

Hope this helps,
 -- Guido