Please merge transmission 1.61-2 from Debian unstable (main)

debdiff between 1.51-0ubuntu1 and 1.60-2ubuntu1 is over 12 megabytes in size so I can upload it on request.

I've changed Maintainer to Ubuntu MOTU Developers <email address hidden> as transmission was moved to universe.

When was transmission moved to universe? AFAICT, it's still in main

Other than that, the merge looks ok I think. Have you checked through the open bugs on Launchpad to see if this version closes any of those out? If it does, then you can add the bug report numbers in the changelog so they get automatically closed out (in the format "LP: #xxxxxx"). You should subscribe ubuntu-main-sponsors to this bug report once it's ready.

Thanks:)

As a start, this release fixes bug 183473, so that should get a mention in the changelog really.

Hmm.. interesting..
thansmission-gtk and transmission-common is still in main but transmission and transmission-cli are in universe.. I got confused because of that (didn't know that packages from one source package can go to different repos). I'll revert to Core developers and add all bug numbers. Thanks for commens.

* Reverted Maintainer to Ubuntu Core Developers.
* Closed 4 LP bugs in debian/changelog.

I've found one more bug that is closed in 1.60-2.

If you really want to update, it should be to 1.61 rather than 1.60.

1.61 contains a security update that is important for users who access Transmission via a web browser.

Sigh, I just saw it released on #transmission channel. I'll prepare another debdiff when Debian Maintainer uploads 1.61 to repository. Thanks for a comment. :)

No need to stall on Debian. Now you've rebased on Debian, you could also update to 1.61 in the same upload ;)

On Tue, May 12, 2009 at 9:53 AM, Chris Coulson
<email address hidden> wrote:
> No need to stall on Debian. Now you've rebased on Debian, you could also
> update to 1.61 in the same upload ;)

There is one more thing I'd like to sort out with Debian Maintainer (a
status of https://bugs.launchpad.net/bugs/338671 and the fix he has
used for it) before we merge packages so until I get a response I'd
like to hold it back a while.

I have prepared updated debdiff for merge of 1.61-1 from Debian Unstable. In fact I have prepared two debdiffs:
- First one is, which is attached to this comment, is the same as transmission_1.60-2ubuntu1.debdiff. Only version is bumped.
- The second one disables ipv6.patch which was added by Debian developer to enable IPv6 support for connection to the tracker. It is https://bugs.edge.launchpad.net/bugs/338671 in Launchpad.

Now, the decision to disable ipv6 patch and not resolve bug 338671 is because Transmission developers believe that this fix is doing more harm than good. You can read whole bug report on http://trac.transmissionbt.com/ticket/1731 and following is quote from Transmission developer:
"For 1.5x and in trunk currently, IPv6 DNS resolution in libcurl (the library we use for tracker communication) is disabled to prevent breakage of trackers with AAAA and A records on the same hostname (notably, TPB)". He has also stated that TPB is the only case he knows but most likely not the only one.
I have contacted debian maintainer about this patch but so far I got no answer. I'd like to know what other, more experienced Ubuntu developers are thinking about it. It won't be possible to sync transmission with debian anyway because of the few changes we have to make (most notably custom Provides and Replaces sections) so we can't remove delta for another few years anyway (Until the end of support for 8.04 LTS).

And here goes second debdiff with ipv6.patch disabled.

ipv6.patch was removed from debian package so I'm requesting new merge.

One more. This time I've added Launchpad Integration requested in bug 359260. I think that's the last one.. :)

Some more cleanup for debian/rules.

Uploaded, thank you!