CollabNet Subversion 1.5.0 binaries available

The first set of our binaries for CollabNet Subversion is now available.  Specifically, the RPM’s for Red Hat Enterprise Linux.  You can get them here:

These are certified to run on all 32-bit versions of RHEL 4 and 5.  In my experience, they run fine on any version of Linux that allows you to install an RPM.  I have even used them successfully on Ubuntu and Debian by using the alien package, which allows RPM to be installed on Debian systems.

Starting with this release of CollabNet Subversion, our Linux RPM’s are now signed.  You can (and should) download and import the GPG key they were signed with.  This was something several of our customers had asked for.  See the readme for the Linux binaries for details and instructions.

As I mentioned in yesterday’s post, we plan to have the Windows binaries available next week.  Currently it looks like they should be available sometime on Monday.  The Solaris binaries will be posted around the end of the week.

We are pretty excited about this release of the binaries.  We put a lot of effort into improving them and what we include in the packaging.  Here are some highlights:

  • Standardized set of dependencies across platforms.  Apache 2.2.8, APR 1.2.12, Neon 0.28.2.  Our Windows binaries initially went out with Apache 2.0 so we wanted to wait for Subversion 1.5.0 to make the switch.  There are upgrade considerations in moving from Apache 2.0 to 2.2 that Windows users will have to consider.
  • ViewVC included!  This is the biggest feature.  Not only do we include ViewVC 1.0.5, but we configure it for you automatically (if you ask us to).  It has never been easier to integrate this excellent tool into your environment.
  • Python bindings are included.  These are needed for ViewVC, but also allow you to use hook scripts that require the bindings, such as the commit email hook script.
  • JavaHL bindings are included with the client.  This makes it easier than ever to use JavaHL on all supported platforms, which means it is also easy to use the CollabNet Desktop and our exciting new Merge Client.
  • SASL support is included in the client and server.  This is a new feature in 1.5.  There is not a lot of information out there on how to build and include it.  We have figured it out though, and include it in our package.
  • We package the svn-populate-node-origins-index program so that you have the tools you need to migrate existing repositories to Subversion 1.5.
  • As always, we provide packages using the native packaging format for each operating system.

These are the main enhancements I can think of, but we have been working on these improvements throughout the Subversion 1.5 life-cycle.  Those of you that participated in our Beta program have likely already experienced some of these new features and seen the packages evolve over the life of the program.  Probably the biggest benefit of our packages is that we test and certify the entire stack that we provide to you.  We do this so that we can provide the level of support that our customers ask for and so that we can be confident that we can deliver on the SLA that we provide to our customers.

Anyway, look for those Windows and Solaris binaries next week.  Also, stay tuned for some additional major new enhancements we will make to the packaging over the course of the summer.  That is all I will say for now, but details will be coming out as we roll out these enhancements.

Mark Phippard

Engineering manager for several teams at CollabNet, including CloudForge, Subversion, Subversion Edge, Git and our Desktops and Integrations. Project owner for the Subclipse project, which provides Subversion support in Eclipse. Also a full committer for the Subversion project. Product owner for GitEye, Subversion Edge and the CollabNet Desktops and Integrations.

Posted in Subversion
15 comments on “CollabNet Subversion 1.5.0 binaries available
  1. rajesh says:

    Hi Mark,
    Are you guys going to release a 64 bit version for redhat 4 or 5?

  2. Joel Natividad says:

    Second Rajesh on the 64-bit builds for RH.

  3. Mike Failing says:

    It is good to see Subversion 1.5 finally released. The SVN portion of the release passed our testing but there is a small problem with using LDAP and the newer Apache 2.2.8 support that is bundled with SVN 1.5 for Windows (CollabNetSubversion-server-1.5.0-22.win32.exe).
    The issue was verfied on two machines. The first machine had the previous release uninstalled and previous directories deleted. The second machine never previously held this software.
    The problem is that LDAP Authentication aborts with an error as shown in this error log snippet:
    [Fri Jun 27 13:16:37 2008] [notice] Apache/2.2.8 (Win32) DAV/2 SVN/1.5.0 configured — resuming normal operations
    [Fri Jun 27 13:16:37 2008] [notice] Server built: Jun 23 2008 13:07:40
    [Fri Jun 27 13:16:37 2008] [notice] Parent: Created child process 3560
    [Fri Jun 27 13:16:38 2008] [notice] Child 3560: Child process is running
    [Fri Jun 27 13:16:38 2008] [notice] Child 3560: Acquired the start mutex.
    [Fri Jun 27 13:16:38 2008] [notice] Child 3560: Starting 250 worker threads.
    [Fri Jun 27 13:16:38 2008] [notice] Child 3560: Starting thread to listen on port 80.
    [Fri Jun 27 13:17:14 2008] [notice] Parent: child process exited with status 3221225477 — Restarting.
    Our LDAP configuration for Apache was updated per release 2.2 changes:
    LoadModule ldap_module modules/
    LoadModule authnz_ldap_module modules/
    DAV svn
    SVNParentPath d:/svn_repository/
    SVNListParentPath On
    AuthzSVNAccessFile d:/svn_repository/access.txt
    AuthName “Local Test SVN”
    AuthType Basic
    AuthBasicProvider ldap
    AuthzLDAPAuthoritative off
    Require valid-user
    AuthLDAPBindDN ********
    AuthLDAPBindPassword ********
    AuthLDAPURL “l********/DC=********,DC=com?sAMAccountName?sub?(objectClass=*)”
    After deciding that our configuration was correct I played a hunch and pulled the files and from the current Apache 2.2.9 distribution to re-test. Replacing those two files resolved the issue for us so that appears to be where the problem might be.
    I look forward to an update soon as I am not comfortable going production with this workaround.

  4. Clemens Anhuth says:

    Why is a login required for the downloads? Aren’t there better target audiences for push-around, force-into marketing than software developers and administrators? Isn’t it good enough to get all the people wanting the Windows binaries onto your site? Do you really need them to register for yet another login? :/

  5. Joel Natividad says:

    Hi Mark!
    Saw your postings on regarding some packaging problems on Ubuntu Hardy which may delay the release of SVN 1.5 on the Ubuntu repositories.
    So after fighting with compiling from source for the past day, I thought I’d go the alien route and convert the RPMs to DEBs.
    The Client installed without a problem. However, the Server won’t go in.
    Any hints on how to get the Server going on Hardy?
    More power to CollabNet!

  6. Joel,
    Can you bring this to our discussion forum and include more details on the problem you see?
    The server RPM requires the client RPM. Perhaps the problem is related?

  7. Joel,
    I also recall the server requires that the LSB Debian packages are installed so that the init.d scripts that are included work.

  8. Pat Podenski says:

    What ever happened to the binaries for Solaris v1.5?
    Is there any estimate of when these will be released?

  9. Matt Block says:

    Another vote for 64 bit versions of the subversion client/server for RHEL 4/5. It would be nice if someone from collabnet would post if this is planned or not.

  10. Joseph Bell says:

    +1 for a 64-bit version RPM for RHEL 5!

  11. David Carsey says:

    RHEL5 x64 bit is needed for our upgrade to 1.5

  12. Sergio B. says:

    Another vote to RHEL4 and RHEL5 x64 packages.

  13. Did you all see the blog post earlier this week announcing that these are now available?

  14. Snakefoot says:

    Hi ya
    I have tried looking at the Release-notes and very little is written about the different upgrade paths.
    0) Update the binaries without touching the the repository (Allowing one to go back to 1.4)
    1) Run the “svnadmin upgrade” command to update the repository. Maybe consider running svn-populate-node-origins-index.
    2) Dump the repository, upgrade the binaries and reload the repository
    Is there a recommended upgrade path ?
    If the repository already have been through several feature branches, that have been merged back to trunk. Is it possible to run a manual command that will update mergeinfo for these old commits ? (To get better log and blame details)
    Best regards

  15. Rolf,
    You might take a look at the free training course we offer here:
    I *think* it touches on some of the upgrade issues.
    As for the rest of your questions, I do not really like trying to have a “discussion” in blog comments. So please start a thread in our Subversion discussion forum.

Leave a Reply

Your email address will not be published. Required fields are marked *