[Kolab-devel] Debian packages - where to commit changes - dependencies

[Timotheus Pokorra]

Hello Jan,
I am glad that you are working with OBS!

> First: great, with the actual nightly builds I was able to set up kolab 31 on
> two separate servers - one only for ldap and another for imap/mta/roundcube
> and most thinks work fine - including file and addressbook now (with some minor
> problems).
Please also report the minor problems in Bugzilla.

> I'd like to help improving the packages with their dependencies for a
> distributed setup - and have still some questions how the process works. Sorry
> I'm making my first steps and still (and I'm afraid also in the future) have
> very little knowlede about package building and obs so please apologize my
> questions:
No problem at all! Glad to cooperate on this!

> For example: I added one dependency to pykolab debian package (libpython2.7).
> For this I only changed the debian.control. Maybe the problem is the same for
> other distributions? What to do in this case? Are the dependencies managed at
> a central place or separately for each distribution? What would be helpfull to
> change?
debian.control is for all deb based packages, that means for Debian and Ubuntu.
The dependencies for the rpm based packages are in the *.spec file,
for CentOS and Fedora and OpenSuse. I guess we should keep things
separate between deb and rpm packages. So if we find a problem with
deb packages, we report it in Bugzilla in the debian packaging area,
and fix it only for Debian. If someone finds the same problem with
CentOS, he can report it in the rpm packaging area in Bugzilla. We
still can check how the other packaging does things, but I guess we
should not change in the "other" distribution if we are not completely
sure about the effects.

> Because there where newer packages than the Kolab:Development in your nightly
> repos I branched your repo, made the change and submitted it (you've propably
> seen the request). Does this make sense? I've tested it with the nightly
> builds.
Your request makes sense.

> Or do I have to commit it against the Kolab:Development for not loose the
> changes in the release? But where the rules for the nightly builds come from?
> Are they all equal to the Kolab:Development only with the difference of newer
> source code?
Yes, it is better to commit against the Kolab:Development project.
The difference of the nightly project is that each night the latest
tar.gz files from git.kolab.org are uploaded, but the package sources
are inherited from Development.
The script that is run every night is described here:
http://docs.kolab.org/developer-guide/nightly-builds/create.html#nightly-update

You can see the difference of the nightly package for pykolab and the
Development package here:
https://obs.kolabsys.com/package/rdiff?opackage=pykolab&oproject=Kolab%3ADevelopment&package=pykolab&project=home%3Atpokorra%3Abranches%3AKolab%3ADevelopment&rev=40

The nightly packages are quite experimental, and I cannot submit
things from nightly to development because the nightly source files
would go up as well.
About the changes that you need from the nightly packages: I wonder at
what point we can update the tar.gz file in the Development packages.
I guess that should be done as a proper release tag in git? You see I
have questions myself...

I have now derived pykolab from Development and applied your patches,
and I will commit that to Development later tonight.
This will turn up in the nightly packages (though I usually have to
manually fix merge conflicts, somehow the changelog and version info
does not merge well).

> A lot of questions ....
>
> Thanks and regards
You are welcome!

All the best,
  Timotheus