Please backport tor-arm 1.4.0.1-2 from natty to lucid, maverick

[Damian Johnson]

Hi, a package I maintain (tor-arm) has just been added to the natty repo:
https://launchpad.net/ubuntu/natty/+source/tor-arm/1.4.0.1-2

This is a CLI monitor for Tor relays. The project page is available at: http://www.atagar.com/arm

This package doesn't require any modifications and only effects itself. I'd like to request a backport of the package to the last three Ubuntu releases: 10.10 (Maverick), 10.04 (Lucid), and 9.10 (Karmic). Should I file separate tickets for each or is a single ticket sufficient? Thanks! -Damian

[Evan Broder (broder)]

Hi Damian,

At this point, we can no longer backport to Karmic as it has been end-of-life'd, but we can still backport to Lucid and Maverick. A single bug is sufficient, but in the future you can open a separate "task" for each release to which you'd like to backport by using the "Also affects project" link. (I've gone ahead and done so)

Before we can approve a backport, it's important to have some basic testing on packages generated as they'll be generated by the backports process. I've uploaded test backports of tor-arm for both lucid and maverick to my PPA (https://launchpad.net/~broder/+archive/backports-tests). Please verify that they successfully build, that you can install the packages from that PPA, and that you can run the packages (or otherwise exercise some basic functionality) once you've installed them. This verification needs to be done on both lucid and maverick.

Feel free to change the status of the bug to "Confirmed" once this verification has been done.

[Damian Johnson (atagar1)]

Thanks Evan. I've tested the packages, using them to monitor a Tor relay. Both look good. -Damian

[Damian Johnson (atagar1)]

Ack, missed the last bit of the comment - I installed and ran them both on karmic but not maverick/lucid. This is a pure python package and been exercised on several Debian, Ubuntu, Gentoo, Arch Linux, and Slackware versions already without any platform-specific issues. If it's really _vital_ that I set up a maverick and lucid vm to test this again I can. However, that would be a lot of work for what, in reality, would be a pointless test (it would just be checking yet again that python is cross-platform).

[Evan Broder (broder)]

Our experience has been that this test is not pointless, which is why it is a hard requirement for the backports process. Testing inside of a lucid/maverick chroot is acceptable, but testing on a different release is not.

[Damian Johnson (atagar1)]

Found a volunteer that tested on lucid (10.04), still trying to find someone with maverick.

[Kamran Riaz Khan (inspirated)]

Confirmed working on Maverick (although the "tor-arm" package lists "tor" as a suggested package instead of dependency).

[Evan Broder (broder)]

Great, thanks for the testing. ACK from backporters.

[Colin Watson (cjwatson)]

I: Extracting tor-arm_1.4.0.1-2.dsc ... done.
I: Building backport of tor-arm as 1.4.0.1-2~lucid1 ... done.

[Colin Watson (cjwatson)]

I: Extracting tor-arm_1.4.0.1-2.dsc ... done.
I: Building backport of tor-arm as 1.4.0.1-2~maverick1 ... done.