Re: [Deluge] #3231: Changing priority behaves strangely.
Deluge
----------------------+------------------------
Reporter: loput | Owner:
Type: bug | Status: new
Priority: major | Milestone: 1.3.16
Component: Unknown | Version: 1.3.15
Resolution: | Keywords: gtk web ui
----------------------+------------------------
Changes (by int3l):
* keywords: => gtk web ui
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3231#comment:3>
Deluge <https://deluge-torrent.org/>
Deluge Project
Deluge
----------------------+------------------------
Reporter: loput | Owner:
Priority: major | Milestone: 1.3.16
Component: Unknown | Version: 1.3.15
----------------------+------------------------
Changes (by Cas):
* status: new => closed
* resolution: => WontFix
Comment:
This is a problem with changes in libtorrent 1.1 file priority handling.
The only solution is to use libtorrent 1.0 with Deluge 1.3. I'm afraid
that this will not be fixed in 1.3 however it was fixed in 2.0.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3231#comment:4>
Deluge
----------------------+------------------------
Reporter: loput | Owner:
Type: bug | Status: closed
Priority: major | Milestone: 1.3.16
Component: Unknown | Version: 1.3.15
Resolution: WontFix | Keywords: gtk web ui
----------------------+------------------------
Comment (by PukeMonster):
Sorry, what? WontFix?
Are you serious?
So deluge 1.3.x series is absolutely finished now then?
You're stopping all development and bugfixes on 1.3? Because if you don't
fix this, you might as well throw 1.3 in the bin.
It is completely unusable now.
It is just not good enough to say the problem is in libtorrent 1.1, so we
can't fix deluge.
I've been usign Deluge for as long as I can remember, and i had two
reasons for using it:
1) it works
2) it works well
Deluge now fails both of those tests.
This bug has to be fixed, or there is no point doing any more work on
Deluge, at all.
Please re-open this bug, and fix the issue.
I can think of several possible ways to move forward:
1) Get it fixed in libtorrent. If they're the cause of the issue. How are
they allowed to just completely change the way their priorities work if it
is going to break clients like Deluge? They shouldn't be able to make
changes like that unless they do it in libtorrent 2.0
2) You say the only solution is to use libtorrent 1.0 - so... use
libtorrent 1.0!
If libtorrent aren't going to fix this issue in 1.1+, then, 1.1+ is
unusable, and you need to go back to using libtorrent 1.0. Please advise
how to do this.
Eg, for Windows, pls advise:
1) What was the last version of Deluge which used libtorrent 1.0 and thus
actually *works*.
2) is it possible to get libtorrent 1.0 for Windows and drop it into the
Deluge install folder to overwrite the garbage 1.1, and have things work
again?
3) Will you (pls) package the current and future releases of Deluge 1.3.x,
with a working libtorrent 1.0?!
4) If all of this is too hard, is Deluge 2.x going to be available for
Windows anytime soon, and is it going to be usable? I have already
switched to qBittorrent and if Deluge doesn't become usable again *soon*,
I doubt if i will *ever* bother coming back.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3231#comment:5>
Deluge
----------------------+------------------------
Reporter: loput | Owner:
Type: bug | Status: closed
Priority: major | Milestone: 1.3.16
Component: Unknown | Version: 1.3.15
Resolution: WontFix | Keywords: gtk web ui
----------------------+------------------------
Comment (by PukeMonster):
FWIW, I've just tried going back to 1.3.12, and this appalling bug is not
present in deluge-1.3.12-1-win32-py2.7-setup.exe
As far as I'm concerned, later versions of Deluge may as well not even
exist, until this bug is fixed.
So it's up to you. Fix this bug, or don't fix it. I don't care anymore.
But, you might as well be aware that if you don't fix this bug, everything
else you're doing on 1.3.16+ is utterly pointless.
Carry on.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3231#comment:6>