Re: kolab on openSUSE natively is a little bit back

Op maandag 04 mei 2009 07:15:28 schreef Carsten Burghardt:
> > Op zaterdag 02 mei 2009 03:14:08 schreef Thomas Spuhler:
> >> On Friday 01 May 2009, Richard Bos wrote:
> >> > Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
> >> > > > What version of perl-ldap to you have? I found this link
> >> > > > https://www.intevation.de/roundup/kolab/issue1755
> >> > >
> >> > > Well, the version is perl-ldap-0.39-5.2 from the kolab suse
> >> > > repository but it does not contain the fix. Thanks for spotting
> >> > > this. I assume the package is too old.
> >> >
> >> > It's not.  I have the same and it is working fine.
> >> > kolab2:~ # rpm -q perl-ldap
> >> > perl-ldap-0.39-5.3
> >> >
> >> > At the moment I can't think of a reason why you can't start ldap.  I
> >> > believe I have seen the same thing, perhaps it is mentioned in
> >> > issue1755.
> >>
> >> you have -5.3 vs. -5.2
> >> different build but what else?
> >
> > That's a very minimal difference.  That number is added by the openSUSE
> > build service, when a build is restarted.  This might be triggered by a
> > package that
> > is needed as build dependency for the perl-ldap package.
>
> Well, I installed the package from the kolab suse repository and at  
> least on my system the patch is not included. Once I patched it  
> manually the cookie parsing problem was gone.

After investigating the package on the build service, it indeed misses the 
patch http://git.goingon.net/?p=perl-
ldap.git;a=blobdiff;f=lib/Net/LDAP/Control/SyncRequest.pm;h=d905d7bd1c7ee27c45a9609594fb89e3d9e8d63c;hp=95cd71634aa1c0704408d267a799bbc16915cda4;hb=3c5a803879e213ef146fad42f194e6f3568c6358;hpb=48fb4340597d60813f526a5a0217a36a04017d34
That one was created just after the 0.39 release.  I have updated the package 
on the build server, and is has been reported to work for openSUSE_10.3 in the 
meantime already.  Thanks Alar!

--

-- 
Richard