The kicker for me is Zach's statement above: In short, Deluge isn't really done yet, and it's still in rapid development, which is why I'd almost rather it not be in the repository at all, sadly. I just don't want users to look at whatever version winds up packaged in the repositories and think that it's "done."[0]
Considering that we should err on the side of conservative measures because we are fewer than FOURTEEN days from release, we should push for the binary removal of the current version if there is no straightforward manner in which to backport a fix for the "it does corrupt most of its downloads" issue[1]. If a binary removal is not possible, then we should simply push for a source+binary removal. Keep in mind that feisty+1 opens soon, and a newer source version of deluge-torrent is a candidate for feisty-backports. With the above three points in mind, I am stating a vehement -1 for this UVF exception. [0] https://bugs.launchpad.net/ubuntu/+source/deluge-torrent/+bug/90749/comments/21 [1] https://bugs.launchpad.net/ubuntu/+source/deluge-torrent/+bug/90749/comments/2 -- Deluge 0.5 in feisty https://bugs.launchpad.net/bugs/90749 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
