Backports, and why you shouldn’t just follow my directions

I got hooked on Bazaar (or bzr – which is the package name) shortly after I started working in Ubuntu. It’s a great version control system written in Python, and I’ll show a nice example of its use here soon. But that’s not what this post is to be about.

Looking for bzr in the Etch repository, I found that a plain aptitude install bzr would provide me with version 0.11 of the software. Now, that is a lot of versions away from the current stable version, 1.1. So I decided I couldn’t do without a newer version, and since I trust the package to work well and it doesn’t provide any network services (so security risks are limited), I thought I might as well get the newest version from the developer site.

At that point I remembered backports. A quick look around the site told me bzr 1.0 for Etch was available from there. Now, there are a few advantages to using a back-ported deb package over a manual installation. One of them is the ease of installation (after adding to your trusted sources as explained here, the back-ported packages are available in your package manager), but in fact installing bzr by hand is also really simple: unpack the tarball in a suitable place and put a link to bzr in your path.

The real reason I opted for backports is that using the package manager makes the package management system aware of the presence of a version of bzr on your system. This gives you lots of benefits: you get warned when you try to install an incompatible package, when you install another version, or when you remove a package that bzr depends on.

Well then, I added backports to the trusted sources as described in the given link, and used aptitude to select the 1.0 version. You need to explicitly select the newer version, otherwise the system defaults to installing the official repository version (you can use pinning to alter this behaviour, but that’s a topic I’ll have to skip for now). I chose not to install the recommended packages bzrtools and python-paramiko (for sftp support), which you would also have to manually set to the right versions if you have a need for them. That’s all!

Almost all. There’s one essential remark I usually don’t see in blog posts like this one: there is of course a reason why backports are not enabled by default on your Etch system. If, like many people, you’ve come to Debian for its reputation of good security, you need to realise that it is only as secure as you keep it. You are the only person who can assess the implications of adding a repository to your trusted sources, and it’s not a decision to take too lightly. I trust backports as a source, and I trust bzr 1.0 to be stable enough to belong in an Etch system, but you shouldn’t just jump off that cliff with me…


5 Responses to “Backports, and why you shouldn’t just follow my directions”

  1. 1 yungchin 25 April 2008 at 1:02

    “It’s a great version control system written in Python, and I’ll show a nice example of its use here soon.”

    Well, soon became two months later… :P

  2. 2 KR 18 September 2008 at 22:09

    I want to get started with BZR. But I am hitting some roadblocks.
    Basically, the setup I want is to have a repository on my NAS device and have check-outs/check-ins from my Desktop/Laptop which ever.
    I want to make this similar to my Clearcase which I use at work.
    Is there a step-by-step for a newbie?
    Thanks in advance.

  3. 3 yungchin 18 September 2008 at 22:43

    Hi KR, well I’ve never seen Clearcase but I assume bzr would be most similar if you use it in the “team collaboration, central style” setup. For the examples given there you should then replace the sftp-address by the path at which your NAS file system is mounted (or if you like I guess it will have sftp too…).

    Hope that helps. By the way, bzr also has some pretty decent built-in documentation; you can type “bzr help ” (e.g. “bzr help commit”).

  4. 4 KR 19 September 2008 at 14:48

    Thanks Yungchin.
    Actually I wanted to try it out, myself. But I wanted to see if there was any step-by-step guide someone had posted, to avoid re-inventing the wheel.
    Anyway, I will post my experiences here, if it is allowed.

  5. 5 yungchin 20 September 2008 at 6:30

    Hi, that’s cool – you’re very welcome to post them here of course, but the comments section has very few formatting options. Since starting a WordPress blog here is free maybe that’s more convenient for a longer post?

Comments are currently closed.

%d bloggers like this: