Please sync deluge (1.0.7.dfsg-3) from Debian experimental

I support this change.

Please make it a priority.

I spoke with zachtib about this earlier. We are way past feature freeze and in beta freeze also. Is there a really critical reason why this version must be in Intrepid? The developer felt indifferent about the inclusion and I'd personally rather not take the risk at this point in the release cycle.

I understand it is late in the freeze. There is no critical reason to have this version, other than it being "Version 1" and all the associated changes that come with it (see bug description). I think it's fair to say this is Won't Fix for Intrepid.

For anyone that wants to use 1.0 in intrepid, there are intrepid packages in my PPA.

http://launchpad.net/~deluge-team/+archive

Also, I'd like to look into getting it backported sometime after the intrepid release

Reopening / triaging for Jaunty. Hopefully we can sync this from Debian when it appears.

Debian has two upgrade requests for deluge, and neither are moving. Can we get the 1.0.6 deluge-team packages in jaunty and intrepid-backports?

From a quick interdiff it seems like the packaging has changed significantly since the current Ubuntu package. It would need to be more thoroughly reviewed, not just a trivial pull-from-PPA job.

"changed significantly" is a serious understatement. 1.0 is a
complete rewrite from 0.5.x. nothing is the same.

On Thu, Dec 4, 2008 at 10:09 PM, John Dong <email address hidden> wrote:
> >From a quick interdiff it seems like the packaging has changed
> significantly since the current Ubuntu package. It would need to be more
> thoroughly reviewed, not just a trivial pull-from-PPA job.

Thanks for that information. Then it seems pretty self-explanatory why Debian efforts are stalling too. May I suggest for the Deluge team or someone interested in pursuing this upgrade to submit the PPA package to REVU? In this circumstance where basically nothing but the name is still common with the old project, I think this is the best thing to do.

Increasing the priority of this task; as it is imperative we don't release Jaunty with an unsupported branch of Deluge!

I'm currently maintaining the PPA, so I guess I could submit it to REVU... any link to a quick howto?

Hey Zach, information on using REVU can be found at https://wiki.ubuntu.com/MOTU/Packages/REVU?action=show&redirect=REVU

I just started testing 1.0.7, and I've already discovered some bugs. (One in the packaging, and one in the program).

I think maybe we need to change how we think of this program. Instead of thinking of it as an upgrade, just think of it as a new program, which is what it is. At a minimum, you could leave the old deluge packages in jaunty, with the deluge name, and add the new deluge as deluge1. This is done with things like grub and java, so I think it would make sense.

Thus, you can incorporate deluge1 now, leave deluge0 for those who don't want to upgrade without an upgrade path, and then merge later on. (though, personally, I don't care about the loss of settings. It keeps the torrents, which is good enough for me.)

Question: since deluge0 is essentially an abandoned project, does it make sense to invalidate all the outstanding bugs in launchpad?

Lastly, the last caveat is a feature, not a drawback. You can still run the daemon all you want, but the default setting for the GUI is to attach itself to the local daemon, and close it when you close the GUI. This is what a single user expects. But, if you want to run the daemon on an ongoing basis, you either have to disable "classic mode" for the gui, or use the web and cli UIs. Anyway, its not that important. Normal users won't notice, and the help docs seemed clear enough for the power users IMHO.

I think this should be handled as a standard upgrade. If 1.0.x is available in Jaunty, would anyone use 0.5.x? I also remember hearing in the OOo 3.0 discussion that it was no longer possible to do versioned packages anyway. This deluge upgrade should be similar to other major version upgrades, I don't think any special process is needed.

As for the 0.5.x bugs, invalidating them is a bit much. It's more appropriate to ask each of them to test with 1.0.x and mark incomplete, and follow the standard procedure for those bugs. I can do that when the time comes.

The new Deluge package has entered Debian experimental and is now at version 1.0.7.dfsg-3. I have tested and built this package in my PPA. I have also filed a bug which has been fixed in the newest revision in order to ensure a clean upgrade from the old deluge-torrent package.

As 0.5.x is unsupported I see no reason to offer both packages in parallel. This would also increase our delta with Debian, and make further upgrades more difficult.

The only thing blocking right now is the need for the new version of libtorrent-rasterbar which provides python bindings. This is also availiable in Experimental. A sync bug for this has been filed. See Bug #275375

http://ftp.debian.org/debian/pool/main/d/deluge/deluge_1.0.7.dfsg-3.dsc

Changing this into a sync request.

A correction and an update...

Obviously the bug number for the libtorrent-rasterbar sync is incorrect as it is the number of the bug you are currently looking at. That should be: Bug #315152 which has received and ACK but not been synced yet.

libtorrent-rasterbar has been synced.

Sync request ACKed.

Here is the debdiff to close the bug. Please sponsor the sync. This is the debdiff against the package in debian: http://ftp.debian.org/debian/pool/main/d/deluge/deluge_1.0.7.dfsg-3.dsc.

@ jsmidt

Thanks for the interest, but as there are no Ubuntu changes required this will be taken care of by an Archive Administrator syncing directly from Debian.

If you want to learn more about the process, look here:

https://wiki.ubuntu.com/SyncRequestProcess

Was autosynced.

In ppa for deluge, there's already 1.1.0, which supports password protected connecting to remote daemon.
Packaging for it din't changed since 1.0.x

Oh, deluge packagers didn't change packaging since 0.5.x

https://edge.launchpad.net/~deluge-team/+archive/ppa

Staying in sync with Debian is important as it means much less work in the long run for Ubuntu. It also means that we can pass fixes back to Debian. After this sync is done, we can build a 1.1.0-0ubuntu1 package if necessary.

The Deluge Team PPA is me, and I'm not actively developing the client anymore, that's markybob and andar now. I see that debian has packaged the client under deluge instead of deluge-torrent, which I'd be all for.

-zachtib

1.1.x should get into Debian soon.. I'm currently working out some licensing issues that has held it back so far.

Hew, I noticed that you had inferred from some discussion you heard about OOo 3.0 that versioned packages are no longer possible. I think you've made an overly general leap there. There were some problems with *specifically* the OOo 3.0 packaging that apparently made it more difficult than before to produce versioned package names - i.e. the support for that specifically in the OOo packaging had bitrotted; none of that applies to any other package.

(Of course, since this particular package builds a deluge-torrent transitional package, it *will* overwrite the old one as far as jaunty users are concerned. This isn't a general statement though.)

[Updating] deluge (0 [Ubuntu] < 1.0.7.dfsg-3 [Debian])
 * Trying to add deluge...
  - <deluge_1.0.7.dfsg-3.dsc: downloading from http://ftp.debian.org/debian/>
  - <deluge_1.0.7.dfsg.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <deluge_1.0.7.dfsg-3.diff.gz: downloading from http://ftp.debian.org/debian/>
I: deluge [universe] -> deluge-torrent_0.5.9.3-1 [universe].

Thanks Colin, I wasn't aware that the problem with versioned packages was specific to OOo.

As the sourcepackage has now changed to deluge in Ubuntu, shouldn't the deluge-torrent sourcepackage be removed from the archive as well?