<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Kopano WebApp v8.1.0-335">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>AW: Update von d-push/z-push in Debian testing?</title>
</head>
<body>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">Hi Carsten,<br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">thanks for your email.</span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">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 <a href="https://packages.debian.org/search?keywords=d-push&searchon=names&suite=all&section=all">https://packages.debian.org/search?keywords=d-push&searchon=names&suite=all§ion=all</a>). Is it then still necessary to have transition packages for this layout?</span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">A development writeup about the z-push provided packaging can be found on <a href="https://wiki.z-hub.io/display/ZP/Packages">https://wiki.z-hub.io/display/ZP/Packages</a> and <a href="https://wiki.z-hub.io/display/ZP/Installation">https://wiki.z-hub.io/display/ZP/Installation</a>. This also mentions that the packages you are missing in your overview are now unsupported and therefore no packages are built for them.</span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">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.<br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">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 </span>z-push-ipc-sharedmemory (in your example this would have been part of d-push-common) and one dedicated z-push-ipc-memcached.</p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;">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).</span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a name="_MailAutoSig"></a><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">Met vriendelijke groet</span><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">, Mit freundlichen Grüßen, Kind regards,</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 12.0pt; font-family: 'Times New Roman',serif;"> </span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">Felix Bartels</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">Head of support & professional services DACH</span></strong></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;"> </span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://kopano.com/"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif; color: windowtext; text-decoration: none;"><img src="https://kopano.com/wp-content/uploads/2016/10/lglqa88y.png" border="0" alt="Kopano-Logo-256_03" width="150" height="36" /></span></span></a></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><strong><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">Kopano HQ</span></strong></span><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;"> </span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">Elektronicaweg 18</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">2628 XG Delft</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">The Netherlands</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;"> </span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;">t: + 31 (0)15 2517712</span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://www.kopano.com/" target="_blank" title="This external link will open in a new window"><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif; color: windowtext;">www.kopano.com</span></span></a><span><span style="font-size: 10.0pt; font-family: 'Arial',sans-serif;"> </span></span></p>
<p style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p>
<blockquote style="border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 10pt;">-----Ursprüngliche Nachricht-----<br /><span><strong>Von:</strong> Carsten Schoenert <c.schoenert@t-online.de></span><br /><span><strong>Gesendet:</strong> Sonntag 23 Oktober 2016 18:56</span><br /><span><strong>An:</strong> Felix Bartels <f.bartels@kopano.com>; Sebastian Kummer <s.kummer@kopano.com></span><br /><span><strong>CC:</strong> pkg-giraffe-discuss@lists.alioth.debian.org; Wolfram Quester <wolfi@sigxcpu.org></span><br /><span><strong>Betreff:</strong> Update von d-push/z-push in Debian testing?</span><br /><br /></span>
<div>
<pre style="white-space: pre-wrap; word-wrap: break-word;">Hallo Felix and Sebastian,<br /><br />now a few days after the Kopano Conference I was able to take a deeper<br />look into the Z-Push packages from Kopano and also into the d-push<br />source package in Debian as well.<br /><br />I believe we all want see actual Z-Push packages in addition to<br />kopanocore and kopano-webapp in Debian Stretch.<br />For this we can after the license change of Z-Push do the debrand of the<br />d-push binary packages back to the z-push naming. This is doable and is<br />more or less a technical thing.<br /><br />We will need for that some transitional packages that depend on the new<br />z-push-* packages to not break existing installations of d-push<br />packages. This needs to be done inside debian/control and some<br />additional information for the users in the Debian.README file.<br /><br />I will do the rework of debian/* in case I got enough free time for that<br />but need for now some information which new z-push package should/will<br />replace the old Debian d-push packages. But .. I have no experience in<br />any usage of z-push so we will need your help. ;-/<br />I CCed Wolfram, maybe he can help here too.<br /><br />For now I've compared the existing packages in Debian with the existing<br />packages in 2.3.2 in the folder build/<br /><br />https://stash.z-hub.io/projects/ZP/repos/z-push/browse/build/deb/debian.control<br /><br />Some package relationships are obvious, some i don't see right now.<br />Unfortunately the existing long description is a little bit to short to<br />see which new package will replace which Debian package. I see the<br />following replacements.<br /><br />Debian old -> Debian new<br />d-push (virtuell) -> z-push (virtuell)<br />d-push-combined -> z-push-backend-combined<br />d-push-common -> z-push-common<br />d-push-imap -> z-push-backend-imap<br />d-push-maildir -> ??<br />d-push-searchldap -> z-push-backend-ldap<br />d-push-vcarddir -> ??<br />d-push-zarafa -> z-push-kopano<br /><br />But some other z-push packages are left over after that comparison.<br /><br />z-push-autodiscover<br />z-push-backend-caldav<br />z-push-backend-carddav<br />z-push-backend-galsearch-ldap<br />z-push-backend-kopano<br />z-push-config-apache<br />z-push-config-apache-autodiscover<br />z-push-ipc-memcached<br />z-push-ipc-sharedmemory<br />z-push-kopano-gabsync<br />z-push-state-sql<br /><br />In all there are a lot of packages (17!) which hopefully can reduced to<br />a smaller count. As we (Guido and me) talked about the webserver<br />configuration files for kopano-webapp on the return trip from Vaalsbroek<br />and the minimisation of config packages this part config packages for<br />z-push can surly be meld together here as well.<br />But I haven't done a deeper look here, first we need to do the package<br />migration.<br /><br />Can you please comment the above associations and give us some further<br />hints?<br /><br />Some URLs for existing stuff:<br />https://tracker.debian.org/pkg/d-push<br />https://anonscm.debian.org/cgit/pkg-giraffe/d-push.git<br />https://stash.z-hub.io/projects/ZP/repos/z-push/browse<br />https://wiki.debian.org/Groupware/Kopano<br /><br />-- <br />Regards<br />Carsten Schönert<br /></pre>
</div>
</blockquote>
</body>
</html>