Have you been plagued by Unicode errors when posting changes? Subversion 1.7.x compatibility problems? SSL errors with self-signed certs on Python 2.7.9+? Well then, today’s release of RBTools 0.7.3 is for you! … and, well, everyone, really. There’s a lot in here you’re going to want.
First off, the Unicode fixes. We had some Unicode-related breakages in past releases, which have been almost entirely eliminated in this release. If you’ve hit any such error before, give 0.7.3 a try.
There are lots of compatibility and behavioral improvements for Bazaar, ClearCase, CVS, Subversion, Perforce, Plastic, and TFS. Patching, for instance, works a lot more reliably across the board. Subversion 1.7.x and lower should start working again as well.
It’s not all bug fixes, though. We have some new features and command line options:
rbt post --stamp will auto-stamp commits with the review request URL.
rbt patch -R can be used to revert a patch from a review request.
rbt land and
rbt stamp now work with Perforce.
- Perforce supports changesets with imported files from remote depots.
- API caching behavior and cookie storage can now be disabled/changed for any command. Useful for hooks and other scripts.
- SSL certificate verification can be disabled on Python 2.7.9+ by using
Those are the highlights! For the complete list of changes, see the release notes.
But wait, we have a couple more announcements concerning our releases:
Better installation through pip and Wheels
We’re now officially releasing Python Wheel packages for RBTools, supporting the latest versions of pip. To install RBTools, simply type:
$ pip install --allow-all-external RBTools
(In the future, we’re hoping to eliminate the need for
As of this release, we’re now signing all builds with our official PGP key. Using gpg, you can verify a build was produced by us by importing our public key and then verifying it against the
.asc signature files from our downloads.
For example, to verify
RBTools-0.7.3.exe was produced by us, download it along with
RBTools-0.7.3.exe.asc and run:
$ gpg2 --recv-key 4ED1F993
$ gpg2 --verify RBTools-0.7.3.exe.asc
(Note that if it complains about the key not being certified with a trusted signature, it’s just because you haven’t signed our key. If you see that message, and the primary key fingerprint is
09D5 06DA BB62 A09E 891D A9F3 2852 91B3 4ED1 F993, it’s good!)
We’ll have documentation covering this in more detail soon.
Thanks everyone, and as always, feel free to reach out with any questions.