Getting Started with the Kolab Groupware OBS

Step 1: Register your Username with the Kolab OBS

Navigate to the following URL to register:

Step 2: Install osc

The openSUSE build system is interacted with using a command-line utility called osc.

To download osc for your platform, please visit:

Select your Linux distribution, and follow the instructions.


The openSUSE Build System does not include updates to packages for the distributions it builds packages for. As such, sometimes the osc package might depend on, or be built, or have been built against old packages in a way that is incompatible with the current state of your system.

Initial configuration for the osc command-line utility would be created when you first run it, but the configuration defaults to using rather than

Consider seeding your configuration by putting the following in ~/.oscrc, changing of course your username and password:

apiurl =


Step 3: Create your Home Project

To be able to submit updates for review and approval, we recommend you first create your home project, which will function as the parent, and hold the repository configuration.

The projects you will be creating in your home project are branches off of the targeted branch. So, for example, if you wish to submit an update for the libkolab package in Kolab:3.1:Updates, you will branch off the package libkolab from Kolab:3.1:Updates, and create a libkolab package in a new project home:vanmeeuwen:branches:Kolab:3.1:Updates.

Taking the home:vanmeeuwen project as an example, pull the configuration of it to your own home project:

$ username=<USERNAME>
$ osc meta prj home:vanmeeuwen | \
    sed -e "s/vanmeeuwen/$username/g" | \
    osc meta prj home:$username -F -

Alternatively, use the following command:


Review the target repository names here, for between the time of this writing and you executing the command, some may no longer be available, and others may have been added.

$ username=<USERNAME>
$ osc meta prj home:$username -F - << EOF
<project name="home:$username">
    <person userid="$username" role="maintainer"/>
    <person userid="$username" role="bugowner"/>
    <repository name="openSUSE_12.3">
        <path project="openSUSE:12.3" repository="updates"/>
        <path project="openSUSE:12.3" repository="release"/>
    <repository name="openSUSE_12.2">
        <path project="openSUSE:12.2" repository="updates"/>
        <path project="openSUSE:12.2" repository="release"/>
    <repository name="openSUSE_12.1">
        <path project="openSUSE:12.1" repository="updates"/>
        <path project="openSUSE:12.1" repository="release"/>
    <repository name="Ubuntu_13.10">
        <path project="Ubuntu:13.10" repository="universe"/>
        <path project="Ubuntu:13.10" repository="main"/>
    <repository name="Ubuntu_13.04">
        <path project="Ubuntu:13.04" repository="universe"/>
        <path project="Ubuntu:13.04" repository="main"/>
    <repository name="Ubuntu_12.10">
        <path project="Ubuntu:12.10" repository="universe"/>
        <path project="Ubuntu:12.10" repository="main"/>
    <repository name="Ubuntu_12.04">
        <path project="Ubuntu:12.04" repository="universe"/>
        <path project="Ubuntu:12.04" repository="main"/>
    <repository name="UCS_3.1">
        <path project="UCS:3.1" repository="maintained"/>
        <path project="UCS:3.1" repository="unmaintained"/>
        <path project="UCS:3.0" repository="maintained"/>
        <path project="UCS:3.0" repository="unmaintained"/>
    <repository name="UCS_3.0">
        <path project="UCS:3.0" repository="maintained"/>
        <path project="UCS:3.0" repository="unmaintained"/>
    <repository name="Fedora_19">
        <path project="Fedora:19" repository="updates"/>
        <path project="Fedora:19" repository="release"/>
    <repository name="Fedora_18">
        <path project="Fedora:18" repository="updates"/>
        <path project="Fedora:18" repository="release"/>
    <repository name="Debian_7.0">
        <path project="Debian:7.0" repository="main"/>
    <repository name="Debian_6.0">
        <path project="Debian:6.0" repository="main"/>
    <repository name="CentOS_6">
        <path project="CentOS:6" repository="epel"/>
        <path project="CentOS:6" repository="updates"/>
        <path project="CentOS:6" repository="release"/>

Step 4: Pick your Poison

At the time of this writing, the Kolab Groupware OBS maintains the following projects:

  1. Kolab Development

    This repository contains the latest and greatest releases upstream, possibly including builds of software that is gravely unstable, does not work and break your system.

    This repository is in the lead for future Kolab Groupware releases, and should be used by packagers and developers in non-production, development environments only, and only by those that are autonomous in supporting such environment.

  2. Kolab $x.$y Updates

    This project provides users of Kolab Groupware with updates to the base release of Kolab $x.$y, where $x and $y are the major and minor version number components of the current stable product stream and ones that are older (and largely unmaintained).

Step 5: Branch off a Package

Having chosen your target destination for the update your are going to be working on, branch off the appropriate package:

$ mkdir -p ~/devel/osc
$ cd ~/devel/osc
$ osc branch Kolab:3.1:Updates libkolab
A working copy of the branched package can be checked out with:

osc co home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab
$ osc co home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab
A    home:vanmeeuwen:branches:Kolab:3.1:Updates
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian-Debian_6.0.control
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian.changelog
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian.control
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian.rules
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian.series
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/debian.tar.gz
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab-0.4.2-cmake-2.8.11.patch
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab-0.4.2-paths.patch
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab-0.5-swigutils.cmake.patch
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab-0.5.tar.gz
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab.dsc
A    home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/libkolab.spec
At revision 217384e71ed2eaaeb0f22058e8b51eec.


This branch starts building immediately, for all the target platforms configured as part of the home:vanmeeuwen home project (for user vanmeeuwen).

Step 6: Update the Packaging & Testing the Changes

First off, you are going to make some changes most likely.

$ cd home:vanmeeuwen:branches:Kolab:3.1:Updates/libkolab/
$ (... make changes ...)

Do not yet commit these unless you are certain the changes work. Instead, attempt a local build:

$ osc build --no-verify $target $spec



is one of the target repository names, such as Debian_6.0, CentOS_6, etc.


is one of the local package specifications, i.e. either the .dsc or .spec of the package.

Step 7: Make Sure the Package is Actually an Update

When you are satisfied with the results of your test build(s), bump the version numbers and release numbers as appropriate, in at least the following files:

  1. The .dsc for the package, if applicable,

  2. The debian.changelog for the package, if applicable,

  3. The .spec for the package, if applicable.

Step 8: Commit the Changes

Once step 1 through 6 are completed, continue with commiting the changes back to the Kolab Groupware OBS:

$ osc ci

See additional osc command documentation for further aid in adding, removing and other such actions.


This will start the authoritative builds on the Kolab Groupware OBS, and it will be those builds you are submitting in Step 8.

Please make sure everything builds correctly on the Kolab Groupware OBS as well, and consider testing the updates before continuing with Step 8.

Step 9: Submit the Package Update Request


By doing so, you are requesting your updated package be made available to thousands of consumers globally.

We would encourage you to execute some Quality Assurance both on the software as well as the packaging, before submitting update requests.

Package updates that supposedly fix one or more issues that do not have corresponding tickets in Bugzilla will be refused.

$ osc sr

Provide an appropriate message with the request, that aids the reviewer(s) in determining the feasibility and impact of accepting your update, such as including the ticket numbers of resolved issues.