Deluge 1.0.3 Released

[andar]

The torrents do get added to the libtorrent session, so they will do their checking and what not, but there is an issue with Deluge's torrent object creation..

Yea, it should have been tested more thoroughly before being released, but I had tested the fix in trunk and didn't think to try it out on the RC branch..

We'll have 1.0.2 shortly that will resolve the issue and in the meantime, people who have been affected by this bug can simply re-add their torrents from ~/.config/deluge/state and they shouldn't lose any data.. All the fastresume files should still be there.

[TychoQuad]

Restoring all my old torrents didn't really go as smoothly as advertised because I have Deluge move my torrents whenever they complete. Readding them all again from the state files started downloading them all again.

[spitfire]

Latest 1.0.2 ebuild for gentoo

Code: Select all

>>> Unpacking source...
>>> Unpacking deluge-1.0.2.tar.gz to /var/tmp/portage/net-p2p/deluge-1.0.2/work
 * Applying setup.patch ...

 * Failed Patch: setup.patch !
 * ( /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 * /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-17936.out

 * 
 * ERROR: net-p2p/deluge-1.0.2 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called src_unpack
 * environment, line 2789:  Called epatch '/home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch'
 * environment, line 1420:  Called die
 * The specific snippet of code:
 * die "Failed Patch: ${patchname}!";
 * The die message:
 * Failed Patch: setup.patch!

setup.patch-17936.out

Code: Select all

~ # cat /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-17936.out
***** setup.patch *****

=======================

PATCH COMMAND:	 patch -p0 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
patching file setup.py
Hunk #1 FAILED at 51.
Hunk #2 FAILED at 304.
2 out of 2 hunks FAILED -- saving rejects to file setup.py.rej
=======================

PATCH COMMAND:	 patch -p1 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p2 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p3 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p4 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored

[andar]

Restoring all my old torrents didn't really go as smoothly as advertised because I have Deluge move my torrents whenever they complete. Readding them all again from the state files started downloading them all again.

You can change the download location in the add torrent dialog..

[andar]

Latest 1.0.2 ebuild for gentoo

Code: Select all

>>> Unpacking source...
>>> Unpacking deluge-1.0.2.tar.gz to /var/tmp/portage/net-p2p/deluge-1.0.2/work
 * Applying setup.patch ...

 * Failed Patch: setup.patch !
 * ( /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 * /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-17936.out

 * 
 * ERROR: net-p2p/deluge-1.0.2 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called src_unpack
 * environment, line 2789:  Called epatch '/home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch'
 * environment, line 1420:  Called die
 * The specific snippet of code:
 * die "Failed Patch: ${patchname}!";
 * The die message:
 * Failed Patch: setup.patch!

setup.patch-17936.out

Code: Select all

~ # cat /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-17936.out
***** setup.patch *****

=======================

PATCH COMMAND:	 patch -p0 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
patching file setup.py
Hunk #1 FAILED at 51.
Hunk #2 FAILED at 304.
2 out of 2 hunks FAILED -- saving rejects to file setup.py.rej
=======================

PATCH COMMAND:	 patch -p1 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p2 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p3 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=======================

PATCH COMMAND:	 patch -p4 -g0 -E --no-backup-if-mismatch < /home/mieszko/overlay/mieszko/net-p2p/deluge/files/setup.patch

=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig   2008-07-15 14:54:35.000000000 +0200
|+++ setup.py    2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored

You no longer need the setup.py patch..

[mickstephenson]

Since I have upgraded from 1.0 to 1.0.2 UPnP port forwarding hasn't worked, anyone having problems with this?

[spitfire]

You no longer need the setup.py patch..

So why it's still in the ebuild?

[andar]

You no longer need the setup.py patch..

So why it's still in the ebuild?

Oh, we should probably remove the ebuild from our site since the newest version is usually available in portage quickly. Please use the version in portage.

[klrspz]

I have 2 quick things I wanted to throw out there:
1) I have deluge start up with my session, and 90% of the time the UI will update immediately, then never again until I select a torrent and hit RESUME, or something that doesn't stop or remove the torrent. Often, the files will continue to download, but it's also often enough that they don't, and I don't realize it since the UI is not repainting/refreshing. My first thought at this point would be something to do with GTK, but I wouldn't even begin to know where to start with that. Here's a pastebin of my gtk apps installed: http://pastebin.com/m152198c4 if anyone had any thoughts on that area that'd be great.

2) The remove finished torrents button (previously like a paintbrush icon) was very useful in clearing out completed torrents; would be GREAT to have that back.

[andar]

I have 2 quick things I wanted to throw out there:
1) I have deluge start up with my session, and 90% of the time the UI will update immediately, then never again until I select a torrent and hit RESUME, or something that doesn't stop or remove the torrent. Often, the files will continue to download, but it's also often enough that they don't, and I don't realize it since the UI is not repainting/refreshing. My first thought at this point would be something to do with GTK, but I wouldn't even begin to know where to start with that. Here's a pastebin of my gtk apps installed: http://pastebin.com/m152198c4 if anyone had any thoughts on that area that'd be great.

2) The remove finished torrents button (previously like a paintbrush icon) was very useful in clearing out completed torrents; would be GREAT to have that back.

1. Take a look at your log files or run deluge from the console to see if you're getting any errors.

2. I removed this because it's hard to define when a torrent is truly finished since you can seed indefinite. If you want to remove all seeders, then select the seeding item in the sidebar, select all and remove.