[Pkg-giraffe-discuss] Questions about new files in kopanocore 8.5

[Carsten Schoenert]

Hi,

I've imported a recent HEAD version of the current master branch of
kopano-core that will become 8.5 one day into our Debian packaging for
the experimental tree.

It was working quite out of the box with only small changes, using
libical3-dev from unstable is working. One thing that was needing some
time to tweak is the new option --with-distro which only allows the
following arguments: suse, sles or rhel

This will break the build on all other platforms if you don't know how
to work around here, I changed configure.ac a bit so I can pass by the
argument debian here which will do simply nothing later, we (Debian) use
copied and sometimes modified init scripts and systemd unit files at all.

But this email is more about some new files in the build.
I've tried to tweak me check script to catch up any file and search for
them within the packages. Currently it's not very intelligent but it
found some files we don't have entries for in the install sequences.

> [1/417] processing dh-exec.TR1TpeRM    (from debian/tmp)
> *** dh-exec.TR1TpeRM could not be found in any Debian package!

Can be ignored, temp file from dh-exec.

> [2/417] processing 7.0    (from debian/tmp/etc/php)
> *** 7.0 could not be found in any Debian package!
> 
> [3/417] processing conf.d    (from debian/tmp/etc/php/7.0/cli)
> *** conf.d could not be found in any Debian package!
> 
> [4/417] processing mapi.ini    (from debian/tmp/etc/php/7.0/cli/conf.d)
> *** mapi.ini could not be found in any Debian package!

All above can be ignored, files/folders are packaged into php-mapi.

> [5/417] processing bash_completion.d    (from debian/tmp/etc)
> *** bash_completion.d could not be found in any Debian package!

Stupidity of the script, that folder isn't used that way.

> [6/417] processing logrotate.d    (from debian/tmp/etc)
> *** logrotate.d could not be found in any Debian package!

Same as above, packaged into kopano-common.

> [7/417] processing dagent.cfg    (from debian/tmp/etc/kopano)
> *** dagent.cfg could not be found in any Debian package!
> 
> [8/417] processing monitor.cfg    (from debian/tmp/etc/kopano)
> *** monitor.cfg could not be found in any Debian package!
> 
> [9/417] processing ical.cfg    (from debian/tmp/etc/kopano)
> *** ical.cfg could not be found in any Debian package!

Packaged into {kopano-dagent,monitor,ical}.

> [10/417] processing presence.cfg    (from debian/tmp/etc/kopano)
> *** presence.cfg could not be found in any Debian package!

But here are a lot more files that are not in any sequencer file.

> root at i5:/tmp/buildd/kopanocore-8.5.0~beta0+a069350b# find debian/tmp debian/kopano-* debian/php-mapi debian/python-* | grep presence
> debian/tmp/etc/kopano/presence.cfg
> debian/tmp/usr/lib/python2.7/dist-packages/kopano_presence
> debian/tmp/usr/lib/python2.7/dist-packages/kopano_presence/plugin_xmpp.py
> debian/tmp/usr/lib/python2.7/dist-packages/kopano_presence/__init__.py
> debian/tmp/usr/lib/python2.7/dist-packages/kopano_presence/plugin_spreed.py
> debian/tmp/usr/lib/python2.7/dist-packages/kopano_presence-0.1-py2.7.egg-info
> debian/tmp/usr/lib/systemd/system/kopano-presence.service
> debian/tmp/usr/sbin/kopano-presence

In which package this files should go? I guess we don't want to create
one more package. If we put this all into kopano-utils the package
descriptions needs some update.

> [11/417] processing archiver.cfg    (from debian/tmp/etc/kopano)
> *** archiver.cfg could not be found in any Debian package!

Packaged into kopano-archiver.

> [12/417] processing attachments_parser.db    (from debian/tmp/etc/kopano/searchscripts)
> *** attachments_parser.db could not be found in any Debian package!

This file isn't picked up yet, I guess this should be placed into
package kopano-search?

There are for sure more small things to adjust, this can be done after a
initial upload of 8.5 into experimental?
The symbols files for this snapshot makes a lot of fun, internal symbol
version is 8.4.90 while package version is 8.5.0~beta0+$(git-hash).

I will clean up the hacky things in my tree and will push the tree to my
GitHub site later. If you agree on the commits I can push this all to
Alioth later. I haven't done any testing yet (no Travis nor local
installation).

-- 
Regards
Carsten Schoenert