[Pkg-giraffe-discuss] Update von d-push/z-push in Debian testing?

[Felix Bartels]

Hi Carsten,



thanks for your email.



As far as I can see the package layout you are speaking about was only used in the unreleased Z-Push 2.1 update, but not in the currently distributed packages (as can be seen here https://packages.debian.org/search?keywords=d-push&searchon=names&suite=all&section=all). Is it then still necessary to have transition packages for this layout?



A development writeup about the z-push provided packaging can be found on https://wiki.z-hub.io/display/ZP/Packages and https://wiki.z-hub.io/display/ZP/Installation. This also mentions that the packages you are missing in your overview are now unsupported and therefore no packages are built for them.



While we designed the package layout how we see it fit, we are more than open for feedback and suggestions on how to make this easier to comprehend for admins. Imho the main goal should be to have both packaged builds mirror each other closely, so that users could easily switch from one to the other.



The goal of this package layout on the other hand was to give admins the possibility to install only the packages they really need. Z-Push 2.3 for example introduced the possibility to have volatile states (used for loop detection) in memcache instead of using php shared-memory (which is still the default if both are installed). This reflects in on package z-push-ipc-sharedmemory (in your example this would have been part of d-push-common) and one dedicated z-push-ipc-memcached.



Having multiple config packages for webserver configuration seemed for us the easiest approach to satisfy the need to support multiple webservers (without directly supplying configuration examples for all these servers).



Met vriendelijke groet, Mit freundlichen Grüßen, Kind regards,

 
Felix Bartels

Head of support & professional services DACH

 
 <http://kopano.com/> 

Kopano HQ 

Elektronicaweg 18

2628 XG Delft

The Netherlands

 
t: + 31 (0)15 2517712

www.kopano.com <http://www.kopano.com/>  

 
-----Ursprüngliche Nachricht-----
Von: Carsten Schoenert <c.schoenert at t-online.de>
Gesendet: Sonntag 23 Oktober 2016 18:56
An: Felix Bartels <f.bartels at kopano.com>; Sebastian Kummer <s.kummer at kopano.com>
CC: pkg-giraffe-discuss at lists.alioth.debian.org; Wolfram Quester <wolfi at sigxcpu.org>
Betreff: Update von d-push/z-push in Debian testing?


Hallo Felix and Sebastian,

now a few days after the Kopano Conference I was able to take a deeper
look into the Z-Push packages from Kopano and also into the d-push
source package in Debian as well.

I believe we all want see actual Z-Push packages in addition to
kopanocore and kopano-webapp in Debian Stretch.
For this we can after the license change of Z-Push do the debrand of the
d-push binary packages back to the z-push naming. This is doable and is
more or less a technical thing.

We will need for that some transitional packages that depend on the new
z-push-* packages to not break existing installations of d-push
packages. This needs to be done inside debian/control and some
additional information for the users in the Debian.README file.

I will do the rework of debian/* in case I got enough free time for that
but need for now some information which new z-push package should/will
replace the old Debian d-push packages. But .. I have no experience in
any usage of z-push so we will need your help. ;-/
I CCed Wolfram, maybe he can help here too.

For now I've compared the existing packages in Debian with the existing
packages in 2.3.2 in the folder build/

https://stash.z-hub.io/projects/ZP/repos/z-push/browse/build/deb/debian.control

Some package relationships are obvious, some i don't see right now.
Unfortunately the existing long description is a little bit to short to
see which new package will replace which Debian package. I see the
following replacements.

Debian old        ->   Debian new
d-push (virtuell) ->   z-push (virtuell)
d-push-combined   ->   z-push-backend-combined
d-push-common     ->   z-push-common
d-push-imap       ->   z-push-backend-imap
d-push-maildir    ->   ??
d-push-searchldap ->   z-push-backend-ldap
d-push-vcarddir   ->   ??
d-push-zarafa     ->   z-push-kopano

But some other z-push packages are left over after that comparison.

z-push-autodiscover
z-push-backend-caldav
z-push-backend-carddav
z-push-backend-galsearch-ldap
z-push-backend-kopano
z-push-config-apache
z-push-config-apache-autodiscover
z-push-ipc-memcached
z-push-ipc-sharedmemory
z-push-kopano-gabsync
z-push-state-sql

In all there are a lot of packages (17!) which hopefully can reduced to
a smaller count. As we (Guido and me) talked about the webserver
configuration files for kopano-webapp on the return trip from Vaalsbroek
and the minimisation of config packages this part config packages for
z-push can surly be meld together here as well.
But I haven't done a deeper look here, first we need to do the package
migration.

Can you please comment the above associations and give us some further
hints?

Some URLs for existing stuff:
https://tracker.debian.org/pkg/d-push
https://anonscm.debian.org/cgit/pkg-giraffe/d-push.git
https://stash.z-hub.io/projects/ZP/repos/z-push/browse
https://wiki.debian.org/Groupware/Kopano

-- 
Regards
Carsten Schönert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20161024/fb5232f4/attachment.html>