[pkg-kolab] kdepim and kolab

Paul Boddie paul at boddie.org.uk
Thu May 29 16:02:44 UTC 2014

On Thursday 29. May 2014 07.32.20 Diane Trout wrote:
> > I'm guessing that my available local package for libkolabxml is not new
> > enough, so I'll try and build a newer package and see where I get.
> > Unfortunately, cloning the libkolabxml repository fails at the moment:
> > a
> > fatal: https://alioth.debian.org/anonscm/git/pkg->
> > kolab/libkolabxml.git/info/refs not found: did you run git
> > update-server-info on the server?
> > 
> > Maybe I'm doing something wrong, though.
> Thats a weird git address for alioth.
> I usually use something like:
> git clone git://anonscm.debian.org/pkg-kolab/libkolabxml

Yes, I used the Web interface's details, which works for libkolab but not for 
libkolabxml. Fortunately, the git protocol address worked and I managed to get 
the sources. Thanks for the tip!

> Also it looks like Paul Klos updated libkolabxml back in Nov 2013. Its
> marked as a snapshot in the debian/changelog, and the pristine-tar
> checkout and the copy I downloaded from git have different SHA sums, but
> diffs of extracts of the two tar files seem to be the same.

Well, I built libkolabxml using the packaging details from the above together 
with a recent snapshot of the upstream sources, and the build went without 

I then built libkolab again with the updated libkolabxml package available in 
the local dependencies for pbuilder, and with the small build dependency 
adjustments I mentioned earlier (libboost-system-dev, libboost-thread-dev, 
libossp-uuid-dev, libxerces-c-dev), and this build also went without incident.

So, I suppose I should start to look at testing the results in a system 
completely without libcalendaring. Thanks once again to Paul for his hard 


More information about the pkg-kolab-devel mailing list