The new tarball (hopefully the last for a while) is up now on our
download section.

Ubuntu users should use the following command to install:

$ sudo python setup.py install –install-layout=deb

All other users should do:

$ sudo python setup.py install

Thanks,Adam

The pygtk world used to be quite simple and nice, with good documentation and well known best practices.  These were “static” gtk bindings that someone had to set up by hand (including me for nautilus-python).  These bindings were a pain in the butt to maintain over time but they worked pretty well and were predictable (good for coding against them).  However, a couple years ago the pygtk maintainers decided to abandon these bindings and start from scratch with “dynamic” bindings that would execute the original C code of the gtk library, which would have the effect of dramatically reducing the amount of hand-written binding code the pygtk developers would have to maintain.  These new dynamic bindings have been released for a while but are still pretty new to the world, but for the most part they work pretty well.  As you might be able to tell, the original Nautilus extension used the static pygtk bindings to run, and the new Nautilus 3 extension uses the new dynamic bindings to run.
Running Nautilus 2 with the static bindings works great, and running Nautilus 3 with the dynamic bindings works great as well, but problems start to occur when you try to run Nautilus (2 or 3) with both the static and dynamic bindings at the same time (this is possible).  Unfortunately this is what is happening for many of you right now.  Some extensions are written with the expectation that they can run with a mix of static and dynamic bindings, and if Nautilus 3 loads extensions that try to use the static and dynamic versions of a set of bindings at the same time, it will crash.

I’m not entirely sure what the solution to this is, though it will become less of a problem over time, as people switch completely over to the dynamic bindings.  However, for now, things will be a bit messy and you will have to decide which extensions you want to run.  Right now, the Nautilus 3 RabbitVCS extension uses dynamic bindings.  If you see the following error:

** (nautilus:2259): DEBUG: Syncdaemon not running, waiting for it to start in NameOwnerChanged
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0′ failed
import gobject._gobject
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: specified class size for type `PyGtkGenericCellRenderer’ is smaller than the parent type’s `GtkCellRenderer’ class size
from gtk import _gtk
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_get_qdata: assertion `node != NULL’ failed
from gtk import _gtk
Segmentation fault

Then it means you have another extension running that is trying to use the static bindings.  If you see this error (check in ~/.config/rabbitvcs/RabbitVCS.log) and your Nautilus isn’t able to run, first disable all nautilus-python extensions, then try to run RabbitVCS again.  Then one-by-one, enable your other extensions until Nautilus crashes again.  You should then report the issue either to myself or to the maintainer of said extension.

Hopefully this will resolve itself within a year or so, but until then it will be a somewhat bumpy ride.

Adam

This release is mainly focused on adding Nautilus 3.0 support with the
new nautilus-3.0 client extension.  However, there are quite a few bug
fixes and changes in there as well, including migrating from Glade to
GtkBuilder for dialogs.

Download RabbitVCS v0.15 at:
http://wiki.rabbitvcs.org/wiki/download

Homepage:
http://www.rabbitvcs.org

Note: We should have new packages in our PPA within a few days.

Issue Tracker:
http://code.google.com/p/rabbitvcs/issues/list

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

One disclaimer though: it’s not yet possible to run Ubuntu in Unity mode in a virtual machine, which means I have no way of testing RabbitVCS under Unity. I’ll still try my best to help users if they run into problems, but you need to be aware it’ll be very hard to troubleshoot for the time being.

Let me know if there are any problems with installation!

Well, some of you may have heard about GNOME 3, which is scheduled to be released within a month or two. Unfortunately, the current versions of both nautilus-python and RabbitVCS are completely broken in GNOME 3 because PyGTK has not and will not be ported to GTK+3, and nautilus-python is what RabbitVCS uses to interface with the Nautilus extension framework.  The good news is that not only am I the maintainer for RabbitVCS, I’m the nautilus-python maintainer as well!  I’ve just about gotten the new bindings to work correctly on GNOME 3 and will put out a release as soon as possible.  They will require Nautilus 3 and the next bug-fix release of PyGObject 2.28 (I uncovered a bug in the current version).

The result of all of this is that I will need to port RabbitVCS’s Nautilus client to GTK+3, and possibly the rest of RabbitVCS as well.  It’s going to get a little hairy for a while as we figure out what to do.  So if anyone has any ideas, I’m all ears.

I’m also the maintainer of thunarx-python, which I started originally as a project on github.com, and I recently did my first release as an officially hosted Xfce project!  I just released v0.2.3 last weekend and the project is stable and ready to be packaged by distributions.

Once I get this nautilus-python release out the door, I will start focusing on RabbitVCS bugs once again and maybe make some more progress on advancing towards v0.15.

Happy St. Patricks Day!

Homepage:
http://www.rabbitvcs.org

Download RabbitVCS v0.14.2.1 at:
http://wiki.rabbitvcs.org/wiki/download

Note: We will have new packages in our PPA presently.

Issue Tracker:
http://code.google.com/p/rabbitvcs/issues/list

Adam

• Bug #483. Protect from a key error if no message attribute is present in the log item.
• Fixed the git status to show untracked files as untracked, not normal
• Allow the git status checker to handle repositories in symbolically linked directories
• Bug #486. Fix locale/encoding issues with the date string coming in from git.
• Bug #502 Annotate no longer cuts off lines with closing parentheses in them (it’s a git command line response parsing issue)
• Fix the log context menu command that compares with the previous revision
• Bug #501, Check if the log revision items list is empty before trying to display it
• Bug #499, Don’t show the Working Copy revision in the changes revision selectors
• In the command line, expand specified paths to make it easier to detect working copies
• No more relying on hard-coded paths, now we can install to any arbitrary prefix

There are definitely more bug fixes to come in v0.14.3, but I wanted to get these out the door since my time to work on them is going to be diminished for a while.

Homepage:
http://www.rabbitvcs.org

Download RabbitVCS v0.14.2 at:
http://wiki.rabbitvcs.org/wiki/download

Note: We will have new packages in our PPA presently.

Issue Tracker:
http://code.google.com/p/rabbitvcs/issues/list

Adam

Our next release

Since I started working on this project (2+ years now), there has been a subtle pattern to our releases.  v0.12 was a complete rewrite of the original framework along with a bunch of new functionality, and v0.13 added onto it, filling out the functionality and fixing bugs.  v0.14 was similar to v0.12 in that it pushed some boundaries by adding git support, and I think v0.15 should continue the pattern by filling out the existing functionality and not doing anything too ambitious.  I originally had planned on adding support for another VCS in v0.15, but instead it will be used as a stepping stone for v0.16.

With that said, here is roughly what I’d like to accomplish for v0.15 (subject to changes of course):

• Add a recursive/asynchronous status monitor to the Nautilus extension
• Add RabbitVCS menu items and emblems to the Gedit file browser plugin
• Convert all dialogs from glade to gtkbuilder
• Refactor VCS abstraction code to make it easier to add new VCSs and UIs

These may or may not get done for v0.15 but these are goals.

Looking for contributors

While I will continue working on RabbitVCS for the forseeable future, and I do get occasional help from Jason and Juan, it would be great if more people would contribute to the project, even if in small ways.  If you know python and can spare some time, check out our issue tracker and see if you can fix a bug or implement a feature request.  If you don’t know python but you know some other language, maybe you can work on a new client, like a Windows shell extension, a Mac Finder extension, a KDE extension, or a standalone application for accessing RabbitVCS functionality.  Or if you don’t want to do any programming, you can help keep the website/documentation up to date, manage our translations, or triage bug reports.  You can go as big or as little as you want with your contributions.  I look forward to hearing from you!

Adam