Release announcement for RabbitVCS v0.13.3!

It’s that time again, time for another RabbitVCS point release!  RabbitVCS v0.13.3 brings to the table the following bug fixes:


  • Bug #371, When double-clicking a Previous Message, only the most recent message would be returned
  • Bug #375, Some VCS actions were not prepared to ask the user for authentication.  The result was an error.
  • In the Repository Browser, double-clicking “..” does the correct thing again (goes to parent folder)
  • Bug #371, Allow diffs of directories
  • Bug #363, Prepend the file:// protocol to strings PySVN expects to be URLS
  • Bug #331, Quote URLs when passing them to VCS functions
  • Many other bug fixes

Nautilus Plugin:

  • Bug #296, No longer forces the English language

Gedit Plugin:

  • The v0.13.2.1 release broke the gedit plugin, but it is fixed again with this release.


Download RabbitVCS v0.13.3 at:

Note: Distribution packages and our PPA will be updated within a day or two.

Note2: Ubuntu 8.10 (Intrepid) users should be aware that Intrepid has reached end-of-life status and our PPA packages will no longer build for it.

Issue Tracker:

A big thanks and a great job to everyone on the team and everyone who contributed to this release!


14 responses to “Release announcement for RabbitVCS v0.13.3!”

  1. Jason Heeris says:

    The packages are now published on the PPA :)

  2. zhouheng says:

    Yes! It is the BEST SVN tool in Ubuntu! Thank you so much!

  3. Alex says:

    Great release! Thanks a lot. There are some remaining pet peeves though:

    1) When right-clicking a folder and selecting “Apply patch”, I must select the patch file and _again_ select the target folder (unnecessary step).

    2) After applying a patch, a trimmed text (revis…) is shown (I believe that is a bug). Anyway, it would be much more useful if it listed the affected files.


    • Jason Heeris says:

      The trouble is, there’s no built in SVN support for patching. The entire patching mechanism is done by parsing the piped output of the command line tool “patch” and wrapping it in a Python generator. Hence, once I got to the stage of “it works!” I wasn’t so motivated to keep going to parse out the affected files (decidedly non-trivial).

      But point #1 is valid, have you considered filing an issue so it doesn’t get forgotten?

      • Alex says:

        Hi Jason. Please, look at the issues:

        Issue 395 – Unnecessary step when applying a patch
        Issue 396 – Show some useful information after applying a patch

        Thanks a lot.

  4. demch says:

    Awesome, thanks a lot for all your efforts. =)

  5. photogazer says:

    I have been looking for a substitute for Tortoise SVN on Linux for a long while. This fits the bill perfectly!!! Thanks for the awesome work!

  6. Peter says:

    Good job guys! I love it.

  7. David Yoakley says:

    I’m confused about what a release announcement means. I see point release announcements for v0.13.2 and v0.13.3 and info that says to go to // but the only version I see there is v0.13.1….


    • Jason Heeris says:

      I’m not sure what you mean. Unless I’ve missed something, there are no direct download links on that page, only links to distro specific pages. Can you be more specific? What distro do you use?

  8. David Yoakley says:

    Thanks for the speedy reply Jason. I was looking for ubuntu 10.04 distro for 0.13.3 on the wiki/download pages and not finding it (is it really there as the wiki suggests?). However I was just now able to update via launchpad PPA. It turns out the root issue was just that the ubuntu update manager had politely turned off the PPA source at some point after I installed 0.13.1. I should have checked that first. Sorry for the noise.


    • Jason Heeris says:

      Yeah, we’re trying to move away from the download-site style of deployment for Ubuntu, since the PPAs work so much better. Otherwise it gets too confusing, and we need debs for every distro (it adds up).

      The wiki could probably use some updating though.

  9. Rajesh Rana says:

    It’s cool but Can you guys work on it’s speed for handling Large number of working copy files, it takes ages to open folders, I tried everything to see if it can be corrected but tough luck, today I’ve shifted to KDESVN, I didn’t like it but NO CHOICE.

    I have seen in many of your blog post comments that users are getting frustrated with it’s speed on handling large subfolders and you are defending it but the harsh truth is that it is really slow, kind of give me feeling that I have switched back to Windows OS, but ironically tortoisesvn does pretty well on same set of large files on windows OS.

    Can you please see if you can do something with the speed, even if takes 2-3 secs is pretty fine but the frustration starts when whole system get hangs and takes more than 5-7 secs.

  10. Mike says:

    Just discovered your project and am loving it. One thing I miss from tortoise that is easy to do and I hope you’ll consider …

    When you select two files and right click, could you have an option in your submenu to diff the files (with meld)? I’d like to do this with files even when not under version control as I can under winders.

    Thanks again, ;)