Yes. That is correct. Rebuilding rapidsvn against the current subversion in
EL5.6 fixed it.
In EL5.5, the version of subversion is 1.4 and it got bumped to 1.6 in EL5.6.
After the update, rapidsvn was crashing when selecting a repo from the
bookmarks. A rapidsvn started from the command line will crash and exit with an
error of "segmentation fault" after clicking a repo in the bookmark. I tried
getting a copy of subversion 1.4 from the official repo and installing it.
After that rapidsvn worked again. This hinted me that I should try to rebuild
rapidsvn against the current subversion version of EL5.6.
Basically, I did not modify the spec file to a very different one. I just
converted this
%{?_with_apr1:--with-apr-config="%{_bindir}/apr-1-config"} \
%{?_with_apu1:--with-apu-config="%{_bindir}/apu-1-config"}
to this
--with-apr-config="%{_bindir}/apr-1-config" \
--with-apu-config="%{_bindir}/apu-1-config"
If my understading is correct, the lines
%{?el5: %define _with_apr1 1}
%{?el5: %define _with_apu1 1}
controls the enabling of apr and apu options in the configure part. Since I saw
that those have been assigned with value 1, then I assumed that apr and apu are
enabled during configure. The weird part is I keep failing on rebuilding the
src.rpm file against the current version of subverion with the error "try
--with-apr". Honestly, it drived me nuts. I've even done installing i386
version of all devel packages just to see if it will fix it. I really have
doubts that there is a problem with the spec file. I was going to revert back
to subversion 1.4 when curiosity hit me and decided try to remove the
%{?_with_apr1: and %{?_with_apu1: parts. Then bam! it compiled.
> Could you please submit a pull request with your changes
> here?
>
> https://github.com/repoforge/rpms
Ok, I am new to this. Should my modifications be counted as a submission worth
submitting? I just enabled apr and apu without relying on some other variables.
Those variables did not work for me but I am under the impression that it will
work for the maintainer. So just by rebuilding the rapidsvn against the current
version of subversion, the segmentation fault will be fixed.
IMHO, a request for a rebuild is much better.
Please advise. Thanks!
--- On Mon, 5/2/11, Yury V. Zaytsev <y...@shurup.com> wrote:
> From: Yury V. Zaytsev <y...@shurup.com>
> Subject: Re: [users] rapidsvn-0.9.6-2 segmentation fault
> To: "RPMforge users" <users@lists.rpmforge.net>
> Date: Monday, 2 May, 2011, 11:01 PM
> On Mon, 2011-05-02 at 00:09 -0700,
> Abed-nego G. Escobal, Jr. wrote:
>
> > Not only I have a working rapidsvn but this also gave
> me some
> > additional knowledge! Thanks very much to all!
>
> Could you please submit a pull request with your changes
> here?
>
> https://github.com/repoforge/rpms
>
> Patches floating around the mailing list against unknown
> versions of the
> specs are generally hard to understand and track. I don't
> see what you
> have really changed.
>
> Do I get it right that the rebuild of rapidsvn against
> subversion from
> EL5.6 helped you to sort it out?
>
> --
> Sincerely yours,
> Yury V. Zaytsev
>
> _______________________________________________
> users mailing list
> users@lists.rpmforge.net
> http://lists.rpmforge.net/mailman/listinfo/users
>
_______________________________________________
users mailing list
users@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users
