Deluge 2.x was released 4 months ago. Deluge 1.x and 2.x are not compatible, so people running Deluge in thin-client mode cannot update to the latest version.
Could you have a look at bumping Deluge as there's a patch for libtorrent-rasterbar waiting to be committed and this will break Deluge 1.X-series?
sadly still had no enough time to work on the update. But will try to spend some time this week, since the breaking change is on the way...
Any progress or can we temporarily mark this as broken?
Yes, I built a new port yesterday. Now I need to test it with new libtorrent and potentially sharp couple of angles in the bundled rc-scripts. I expect the updated deluge lands at ports tree this weekend.
Sounds great, thanks for looking into it.
Maintainer's timeout expired.
A commit references this bug:
Date: Fri Dec 20 03:24:08 UTC 2019
New revision: 520459
net-p2p/deluge: Update 1.3.15 -> 2.0.3
Update is necessary because the underlying library libtorrent-rasterbar needs to be updated.
Approved by: rm (maintainer's timeout)
Is this a kind of joke or what? The "update" is just simple as bumping of portversion? Seriously?
Please revert that and mark net-p2p/deluge-cli broken with recent libtorrent.
Port is now broken
net-p2p/deluge also builds fine, and it was a comment from a user that it works. So why revert?
(In reply to Ruslan Makhmatkhanov from comment #10)
I am able to install and run deluge, it connects to peers and downloads torrents.
I am not sure why are you saying that it is broken.
I don't understand how it supposed to work. net-p2p/deluge is just a metaport, that adds some UI dependencies and It even not depending upon libtorrent lol. You didn't update deluge-cli (that is actually depends on libtorrent) - it's still at version 1.3.15.
Comment from what user?
And why you add maintainer timeout? My last response here was two days ago.
net-p2p/deluge may build fine, because it's a metaport, but what problem your commit is solving?
(In reply to Yuri Victorovich from comment #12)
what version of deluge-cli you have installed? If 1.3.15 still working with libtorrent 1.2.2, then what the whole point of this PR?
Sorry, I was under impression that deluge needed to be updated for libtorrent-rasterbar.
It turns out that it wasn't required.
(In reply to Yuri Victorovich from comment #15)
Ok, then please revert your commit to net-p2p/deluge, because it doesn't actually changes anything, but confusing the users. As I said recently, I'm going to update it to 2.0.3 this weekend after proper testing.
@Ruslan Given the incompatibility between major versions, should deluge 2.x potentially come in as net-p2p/deluge2, or net-p2p/deluge copied to net-p2p/deluge1 before updating the current port to 2.x ?
Please test it with the new py-libtorrent patch in the dependency bug.
(In reply to Kubilay Kocak from comment #17)
Can't test if deluge 1.x is working with new libtorrent, because it now broken in ports tree. Anyway, I'm not going to maintain two branches of deluge - just have no time resources for that. My goal was to just update deluge to 2.x and that's all
Hope deluge keep the version 1.3.15
Because most people use deluge for Private Tracker，the most website is not allow deluge 2.0