kolab at klos2day.nl
Thu Dec 12 22:05:37 UTC 2013
Op donderdag 12 december 2013 04:03:48 schreef Mathieu Parent:
> 2013/12/10 Paul Klos <kolab at klos2day.nl>:
> I think you should target jessie (rememeber, remember, the 5th of
> November). If roundcube 1.0 and all Kolab 3.1 deps can be uploaded to
> Debian and migrated to testing before November 5
Well, that gives some time to get things sorted :-). I'll get in touch with whoever packages roundcube, see what they have to say...
> But: I can't find your commits on git.debian.org. Have you done it already?
> > Is there any more intelligent solution to this situation?
> Going backward is a solution also. Mabe cleaner (and people cloning
> the repo are probably following this list).
It's the option I chose, eventually, especially since originially we pulled in the complete packaging history from the kolab package. It's not very useful, because the 'native' Debian roundcube installation differs in a number of quite essential ways.
So, I started over completely, with upstream version 3.0.2. I have not tested the installation itself yet, so currently I don't know if it works.
I followed the instructions here: https://wiki.debian.org/Alioth/Git. I created all repos inside the pkg-kolab group. They can be cloned using:
git clone ssh://$firstname.lastname@example.org/git/pkg-kolab/$repo
Where repo can currently be one of:
There's also pykolab.git, but I haven't done anything yet here. Actually, it might be better to start fresh with the correct upstream version here as well.
If you've already cloned roundcube-plugins-kolab, you'll need to re-clone it.
I haven't figured out how to make these repos public yet; I don't think there's anonymous access either, nor are they browsable.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part.
More information about the pkg-kolab-devel