[pkg-kolab] Questions about packages

Jeroen van Meeuwen vanmeeuwen at kolabsys.com
Mon Jun 25 10:46:03 UTC 2012

On Sunday, June 24, 2012 09:33:41 PM Christopher Reichert wrote:
> On 06/24/2012 01:40 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
> > On 2012-06-24 0:56, Christopher Reichert wrote:
> >> Hey Jeroen,
> > 
> > Hi Christopher,
> > 
> >> I started working on the Debian packages. I emailed all of the old
> >> maintainers and so far I've had no response. Anyways, I have a few
> >> simple questions just so I am on the same page.
> > 
> > Shall we start using the pkg-kolab-devel list on lists.debian.org[1]
> > so our communications is a little more transparent for other people
> > interested in packaging as well?
> Sure, cc'd there now.
> >> What release version is Kolab on? (a.k.a. what version should I
> >> attempt to start working on packages for?)
> > 
> > I had started packaging Kolab 2.4. It's actually more of a product
> > series, though, if you will. For example, we don't really care which
> > version of Postfix or Apache is installed. We do (of course) care
> > about the version of the components for which kolab.org is upstream
> > (i.e. roundcubemail-plugins-kolab, pykolab, kolab-webadmin, etc.).
> Ah, 2.4 ok. I'm just confused by that because the latest release tagged
> in the kolab git repositories are around 2.3. I just want to make sure
> that the debian packages are the exact same as the rhel packages. Maybe
> I am missing something here.

I see where the confusion comes from, git.kolab.org listed "Kolab 2.x 
repositories" but didn't draw a distinction between 2.x prior to 2.4 and 2.4 

> In the Kolab git repos', what is the difference between 'server' and
> 'kolab-server'?

These are both 2.3 repositories.

> >> Are there any good tutorials for install Kolab on CentOS. I was
> >> trying to install Kolab2.4 and I couldn't find the install-kolab.sh
> >> script. Am I doing something wrong?
> > 
> > Please see the Community Installation Guide on docs.kolab.org[2], or
> > www.kolab.org for a quick howto[3].
> Ah thanks, I was using the instructions in the old wikipedia for 2.2.
> > Did you find the existing APT packaging repositories? For example, I
> > have cyrus-imapd[4] and kolab[5] (meta-package), and more[6]. If you
> > could submit your SSH public key to me, then I could issue with an
> > account with sufficient privileges to commit/push and upload to our
> > mirror[7].
> I did find them but not at this URL. They are at
> svn://svn.debian.org/pkg-kolab/kolabd/trunk/. Are they the same?


I do not have access on to push anything to svn.debian.org.

The APT packaging repositories on git.kolabsys.com do list 'kolabd', but this 
too at best is Kolab 2.3.

The best place to start looking at what needs packaging really is:


The basename of each SRPM (no version, release, etc.) represents the package 
name we have an RPM packaging git repository for, and have or should have an 
APT packaging git repository for.

I think we should perhaps try and encapsulate things in a Debian_Packages wiki 
page. I've thought about this before but I found there's too few dimensions to 
a table to encapsulate all information - perhaps we just start with what 
packages we want and what git repo to use (and branches?).

Kind regards,

Jeroen van Meeuwen

Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/attachments/20120625/e2a2a58f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/attachments/20120625/e2a2a58f/attachment.pgp>

More information about the pkg-kolab-devel mailing list