New Repository Addition: Subversion

April 5, 2007 by · 8 Comments 

There have been a few requests in the post comments and via email for a version of Subversion that works with my updated version of httpd. Well, after ripping my hair out for the past couple days trying to get around a few blocking issues, I finally built Subversion packages for 32- & 64-bit systems.

First, unlike my httpd, PHP, and MySQL builds, I wanted to stick with the version of Subversion that came with RHEL & CentOS 4. I really didn't see the point of upgrading to a newer, less tested, version on this particular package. That said, the version of Subversion that comes with EL4 didn't particularly like the version of apr that is included in my repo. That meant that a straight rebuild of the src.rpm wasn't possible (it was failing the apr-related tests during the build).

From that point, I started looking at the newer source packages for Subversion available with FC5, FC6, and in the Fedora development tree. Unfortunately, all of those versions seem to have dependencies for packages that do not exist (or are too old) in the EL4 distribution. Not wanting to have to rebuild a half-dozen more packages just to get this one working, I went searching for an alternative in order to get Subversion 1.1.4 to build with apr versions higher than 1.0.

The solution I found, interestingly enough, was to snag the source package from Dag Wieers. In examination of his spec file, it seems like his build is functionally identical to the RHEL packages, just built & packaged in a slightly different manner. These though, build just fine with newer versions of apr.

That all said, Dag's packages have been rebuilt for httpd 2.2.x and are now available in my repository. Those that requested this addition, please try them out and let me know how they work (to be honest, I don't use Subversion).


8 Responses to “New Repository Addition: Subversion”
  1. Alex says:

    Firstly, once again thanks for all the hard work.

    Now, before I install, I am trying to ascertain what Subversion release this relates to.

    It is labelled as 1.1.4 however the official 1.1.4 version was released in April 2005 and there have been some substantial enhancements and bug fixes since then.

    Has there been a lot of back porting performed? I assume the version from Dag's repository doesn't include any back porting Red Hat may have done? I'll keep researching but any guidance will be much appreciated.

  2. Jason says:

    This version includes all of the patches that are also in Red Hat's spec file. DAG seems to have started with the RH spec file and then moved on from there because 90% of the spec file is identical.

  3. Alex says:

    On reflection I would like to use a more recent (latest stable release) of Subversion.

    I understand that you do not see the point of upgrading to a newer, less tested, version of this particular package however you have also said that you do not use Subversion. I suppose it is the same as all of us wanting to run the latest httpd, PHP, MySQL, etc. which is why we use your repository after all.

    Anyway, I was wondering what your recommendation might be.

    The rpmforge (Dag Wieers) repository has the latest greatest Subversion and mod_dav_svn packages but of course these complain about dependency issues because I am using your http and apr packages.

    Obviously I could install Subversion and mod_dav_svn from source but this seems less than ideal.

    So, should I start with an SRPM from rpmfoge and change the dependencies noted in the spec file to match your packages or should I be starting with an SRPM from yourself and updating to the newer source before compiling? I have a little (very little) experience using SRPMs so this also isn't ideal but seems to be the best option that will allow me to use your repository for httpd, PHP, MySQL, etc. and still use the latest stable Subversion releases.

    Any assistance will be appreciated.


  4. Jason says:

    I'll look into this today, but the best bet for adding a newer version without radically changing functionality (newer versions from Fedora add a TON of deps, some for packages that don't exist in EL4) would be to examine DAG's newest src.rpms and see if they will rebuild with this version of APR.

  5. Alex says:

    Thanks for taking the time to look in to it. I'll do the same but obviously you have a lot more experience of this than I (which is why I am using your repository in the first place) so any assistance will be grately appreciated as always.

  6. Jason says:

    I still haven't gotten around to this but I'm hoping to tomorrow or the next day. I'll let you know what I come up with.

  7. Cassius says:

    Jason, I tip my hat to you with gratitude. I had installed CollabNet's svn rpms, but they are incompatible with trac. I think I will uninstall those rpms and install yours (I already gratefully use your apache2.2 rpms), so I would like to ask: are your svn rpms compatible with trac? Any other requests for trac in this repository? Obvious dependencies are swig and python bindings, etc.

  8. Jason says:

    To be honest, I use Visual Source Safe for my version repository. I have absolutely no idea what will and won't work with the packages I build. I've tried to pick out the most commonly used packages for a LAMP system but some of the outside packages may be broken.

This site is no longer updated. If you have a need for RHEL/CentOS LAMP Stack updates outside the normal channels, I recommend ART.