[Pkg-giraffe-discuss] Bug#865320: kopanocore FTBFS: error: expected class-name before '{' token

[Carsten Schoenert]

Hello Mark,

Am 17.07.2017 um 09:24 schrieb Mark Dufour:
>> The build is for now working but some files in kopanocore have changed
>> in the between time since 8.1.0. Currently I see some files in
>> usr/lib/python2.7/dist-packages/ which aren't not handled by any install
>> helper right now.
> 
> cool! so I guess you are using 8.3.2..?

yes, this was the youngest version I've found on the GitHub mirror.

>> > drwxr-xr-x 2 pbuilder pbuilder    4096 Jul 13 19:51 kopano_migration_pst
>> > -rw-r--r-- 1 pbuilder pbuilder     192 Jul 13 19:51
> kopano_migration_pst-0.1-py2.7.egg-info
>> > drwxr-xr-x 2 pbuilder pbuilder    4096 Jul 13 19:51 kopano_presence
>> > -rw-r--r-- 1 pbuilder pbuilder     187 Jul 13 19:51
> kopano_presence-0.1-py2.7.egg-info
>> ...
>> > drwxr-xr-x 2 pbuilder pbuilder    4096 Jul 13 19:51 zarafa
>> > -rw-r--r-- 1 pbuilder pbuilder     178 Jul 13 19:51
> zarafa-0.1-py2.7.egg-info
>>
>> Do we need these python packages?
> 
> not sure how I missed 'presence' with my previous mail about the
> differences.
> 
> -migration-pst: this is a PST-to-kopano importer, based on the PST
> parser from this project:
> 
> https://github.com/Dionach/PANhunt
> 
> so it's not essential, but it would be nice if we could package it
> (just some python code, plus a copy-paste of the PST parser, as we
> need some patches on our side).
Reminder to myself, I need to expand / adjust debian/copyright then.

> -presence: this is needed for part of the functionality of
> webmeetings in webapp. it monitors for each user if they are online
> in webapp and or XMPP, so other webapp users can see their 
> "presence". so not really essential either, although also a very
> simple python script.
I can remember we had some discussing about webmeetings in the past ...
some more packages to prepare.

> zarafa: I assume this is about swig/python/zarafa? should have been
> in 8.1 I would guess, but this is a very small compatibility thing so
> that older scripts can still import python-kopano using 'import
> zarafa' and catch exceptions with 'Zarafa' in their name. anyway it
> could just go into python-kopano, like we do.
> 
> to summarize, all not really essential, but nice to have and simple 
> python code. well, the presence thing has a dependency on sleekxmpp,
> which I assume is just there in debian atm.. (this gives us some
> issues on other distros.. :P)

Yeah, and in the end no big deal. I think we should put them all into
kopano-utils. But I haven't done any Python packaging at all so I hope
Guido can give some advice.
In the python-mapi package we have included some similar stuff for MAPI*.

https://anonscm.debian.org/cgit/pkg-giraffe/kopanocore.git/tree/debian/python-mapi.install#n9

Is this correct we've done that and can we do the same with the
additional Python things from above?

BTW: We have sleekxmpp already in Debian for Python3 packaged.

https://packages.debian.org/de/sid/python3-sleekxmpp

Should be enough or do you need Python2 bindings?

-- 
Regards
Carsten Schoenert