Bug#835049: deluge is not libtorrent 1.1.0 capable

[Raphaël Halimi]

Control: reopen -1

Hi,

I'm afraid this new upload didn't fixed the problem with the queue not
being updated at all. Torrents initially put in the queue when Deluge is
started, still stay in the queue forever.

Other problems may subsist, since we don't have a complete listing of
those, we can't know.

If you don't plan to introduce 1.0.10 in unstable like I suggested,
please at least warn users with a note (in NEWS.Debian I think) that the
queue is broken due to incompatibilities with 1.1.x, and should be
disabled completely for Deluge to upload torrents as expected.

Thus, re-opening the bug.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#835049: deluge is not libtorrent 1.1.0 capable

[Raphaël Halimi]

Hi,

Although a new version of Deluge (1.3.13) has been recently uploaded to
unstable, it's still pretty broken because of libtorrent-rasterbar
1.1.0: since the queue is not working right, downloading is fine, but no
matter how many torrents you seed, only a few of them will actually be
uploaded since the vast majority will stay in the queue forever.

Upstream libtorrent has released a last 1.0.x version - 1.0.10 - a
couple of days after 1.1.0, and after testing it, I can certify that it
works perfectly fine with Deluge 1.3.13.

More precisely, one month ago, I fetched the git repository of the
Debian packages, and created "libtorrent-rasterbar-legacy" packages on a
separate branch, imported 1.0.10 on them, compiled, and uploaded to my
personal repository; and I also created Deluge 1.3.13 packages depending
on these "-legacy" versions.

I'm pretty sure this would not be acceptable for a public upload to
Debian, since although those "-legacy" packages can co-exist within the
archive with the 1.1.0 ones, they're not co-installable - which means
that people wouldn't be able to install qbittorrent/btfs and deluge at
the same time - but since I lack practice with packaging shared
libraries, perhaps there is a proper way (that I have yet to learn), to
make those packages co-installable. Anyway, for now this is all on my
hard drive (and personal repository), but if you're interested and want
to use it as a start, I can make it available to you.

The bottom line is that Stretch will most probably be frozen way before
Deluge 2.x is available, and in the current state of things, Deluge will
be broken in Stretch if libtorrent-rasterbar 1.1.x is the only version
available in it.

Please do something to avoid that, and in any case, I'd be glad to help.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#835049: deluge is not libtorrent 1.1.0 capable

[Raphaël Halimi]

Hi,

Le 24/08/2016 à 04:22, Andrew Starr-Bochicchio a écrit :
> Thanks for bringing that thread to our attention. It implies that 
> there are some settings that might not be respected rather than the 
> package being unusable. Certainly in my smoke testing, basic 
> functionality is working. Are you seeing any specific issues?

What I saw so far is that the queue system is broken, torrents initially
put in the queue when Deluge is started, will stay in the queue forever.

Also, bug #834403 that I recently filed, may be related (my initial
diagnosis was perhaps too quick, maybe the problem with re-checking data
wasn't related to the presence of both libtorrent versions, but to 1.1.0
incompatibilities - I can't be sure since I downgraded to libtorrent
1.0.7 a couple of days after that - but the problem did seem to
initially disappear after removing 1.0.7, so it may be intermittent).

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#835049: deluge is not libtorrent 1.1.0 capable

[Andrew Starr-Bochicchio]

On Sun, Aug 21, 2016 at 1:08 PM, Marcos Mobley
 wrote:
> Deluge is known not to work with any version of libtorrent after 1.0.9. Of 
> course 1.1.0 was just uploaded to unstable, so it breaks.
> It will not be fixed on Deluge's side for quite some time, it seems.
> Deluge developers are aware of the problem and detail it here:
> http://forum.deluge-torrent.org/viewtopic.php?f=7=53939=10#p224215

Hi Marcos,

Thanks for bringing that thread to our attention. It implies that
there are some settings that might not be respected rather than the
package being unusable. Certainly in my smoke testing, basic
functionality is working. Are you seeing any specific issues?

I've also backported a a number of commits from the soon to be release
libtorrent 1.1.1 related to the Python bindings that should help with
backwards compatibility.

Thanks,

-- Andrew Starr-Bochicchio

   Debian Developer 
   Ubuntu Developer 
   PGP/GPG Key ID: 3B56E2BBD53FDCB1

Bug#835049: deluge is not libtorrent 1.1.0 capable

[Marcos Mobley]

Source: deluge
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Deluge is known not to work with any version of libtorrent after 1.0.9. Of 
course 1.1.0 was just uploaded to unstable, so it breaks. 
It will not be fixed on Deluge's side for quite some time, it seems. 
Deluge developers are aware of the problem and detail it here:
http://forum.deluge-torrent.org/viewtopic.php?f=7=53939=10#p224215


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.3-x86_64-linode70 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)