[Pkg-giraffe-discuss] preparations for kopanocore 8.3.x (or 8.4.x)

Sun Jul 23 10:16:24 UTC 2017

Hello,

now that we have a recent enough gsoap available in unstable I started
to work on the backlog of kopanocore 8.3.x for unstable.

Version 8.3.2
=============
I finally imported 8.3.2 from kopanocore and adjusted my already started
changes more in deep. I modified various install sequencer files to
hopefully get all changes included, also some new files and tools Mark
mentioned. To get a summarize and probably a also TBD I quote Mark from
a previous email.

[quoting Mark]
> -no more dependency on boost!

I removed all B-D on *boost packages. And also on google-perftools.

> -we don't build manpages anymore, and just edit them directly (so no
>  dependency on docbook IIRC)
debian/rules was adjusted to take care on that.

> -there's a new 'kopano-admin' tool I wrote, 'kopano-cli', which can
>  probably just go into kopano-utils
The former is now living in kopano-utils, kopano-cli will come with 8.4
I guess.

> -there are two new migration tools (and packages on our side):
>  migration-imap and migration-pst (resp. PERL and Python).
> -the latter at least bundles the PST parser from:
>  https://github.com/Dionach/PANhunt
> -I think we now use 'librosie' to filter HTML mails. I don't see
>  this in debian (uh oh..)
> -the python-kopano source code has been split up into many files, and
>  there's a new one: lru_cache.py, which is copy-pasted from:
>  http://code.activestate.com/recipes/578078/
Booth tools I placed into kopano-utils now. I adjusted debian/copyright
(not only) due the addition of lru_cache.py. Maybe the mentioned
librosie needs more clarification, I haven't done anything about that
yet. Mark, can you pint to the respective source files?

> -there has been a huge amount of code churn in the form of cleanups
> by jan, so the current patches probably won't apply, if they are
> still needed that is.

Of course the patch queue was needed to tune a bit, but that wasn't that
difficult. But some more eyes on that won't hurt at all.
Please not that the adjustment of the symbols files is really just WIP
and needs further cleanups.

The changes are much more than just 4-5 patches, I pushed my WIP to my
GitHub tree of kopanocore. Some more review appreciated. All changes
above the latest uploaded version 8.1.0-3 are changes we need to talk about.

https://github.com/tijuca/Giraffe/commits/debian/sid

Also the packaging of the additional Python files kopano_migration_pst,
kopano_presence and zarafa in /usr/lib/python2.7/dist-packages/ I
currently haven't done. See also some related previous emails from me:

https://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/Week-of-Mon-20170710/000442.html
https://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/Week-of-Mon-20170717/thread.html

Version 8.4.x ?
===============
I've seen Jan has published a version 8.4.90 instead of a 8.4.0. I don't
know why this version bumping has happen, I suspect where will be a
version 5.0 soon before the next Kopano Conference? Mark?

Lintian
=======
As much as possible I worked also on the lintian checking output.
Currently lintian isn't unhappy of some left over big issues and more or
less normal. Or some kind equal to 8.1.0-3.

> root at x260:/build/kopanocore-8.3.2# lintian -IE ../kopanocore_8.3.2-1_amd64.changes --no-tag-display-limit
> warning: the authors of lintian do not recommend running it with root privileges!
> I: kopano-archiver: hardening-no-fortify-functions usr/sbin/kopano-archiver
> I: kopano-dagent: hardening-no-fortify-functions usr/sbin/kopano-dagent
> I: kopano-monitor: hardening-no-fortify-functions usr/sbin/kopano-monitor
> I: kopano-spooler: hardening-no-fortify-functions usr/sbin/kopano-spooler
> I: php-mapi: hardening-no-fortify-functions usr/lib/php/20151012/mapi.so
> I: kopano-ical: hardening-no-fortify-functions usr/sbin/kopano-ical
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/kopano/libkcclient.so
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcarchiver.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcarchivercore.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcfreebusy.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkchl.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcicalmapi.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcmapi.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcserver.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcsoap.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libkcssl.so.0.0.0
> I: kopano-libs: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libmapi.so.1.0.0
> W: kopano-libs: package-name-doesnt-match-sonames libkcarchiver0 libkcarchivercore0 libkcfreebusy0 libkchl0 libkcicalmapi0 libkcinetmapi0 libkcmapi0 libkcpyconv0 libkcpydirector0 libkcserver0 libkcsoap0 libkcssl0 libkcsync0 libkcutil0 libmapi1
> X: kopano-libs: shlib-calls-exit usr/lib/x86_64-linux-gnu/libkcserver.so.0.0.0
> X: kopano-libs: shlib-calls-exit usr/lib/x86_64-linux-gnu/libkcssl.so.0.0.0
> I: kopano-contacts: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/kopano/libkccontacts.so
> I: kopano-utils: hardening-no-fortify-functions usr/bin/kopano-fsck
> I: kopano-utils: hardening-no-fortify-functions usr/bin/kopano-passwd
> I: kopano-utils: hardening-no-fortify-functions usr/bin/kopano-stats
> I: kopano-utils: hardening-no-fortify-functions usr/sbin/kopano-admin
> W: kopano-utils: binary-without-manpage usr/sbin/kopano-cachestat
> W: kopano-utils: binary-without-manpage usr/bin/kopano-migration-imap
> I: kopano-server: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/kopano/ldapplugin.so
> I: kopano-gateway: hardening-no-fortify-functions usr/sbin/kopano-gateway
> N: 4 tags overridden (4 info)

PHP7.0 vs PHP7.1
================
Currently we hard depending on PHP7.0 and not the default implementation
which is 7.1 currently in unstable/testing. This isn't a big issue I
think as long PHP7.0 will be shipped. But I guess for the next version
Buster the PHP team will ship PHP7.0 within this release. So in the
future we need to address this at some day.

Further working?
================
I think it's probably reasonable to work on the imported version 8.3.2
and prepare a upload to experimental to also get some possible feedback
early. But I also not against importing 8.4.90 if we get some more
enlightening about more needed changes we need to address by this
version. We should focus first on kopanocore to get this source package
ready to get further with kopano-webapp later. And all hopefully while
the Debian DebCamp and Conference in the next weeks.

-- 
Regards
Carsten Schoenert