Deluge 2.2.0 - Merged and Available in all Libtorrent Versions! (Details Inside!)

[ambipro]

https://ftp.osuosl.org/pub/deluge/windows/?C=M;O=D

Complete 2.1.1 -> 2.2.0 changelog is available here

The linuxserver fork of the containers I maintain are now available, see the post viewtopic.php?p=239301#p239301 in this thread.

As always, I recommend libtorrent v1.2.x for torrenting (running a thin client does not matter, just the daemon part). If you are looking for containers (Docker) for this latest version, they will be available shortly. You can always check Help -> About to see which version of the client and server are running and which libtorrent is running.

Hot Tip: I recommend putting the "Tracker" column on the farthest left of the torrent view pane and sliding it down as small as possible. I made a PR that fixes all tracker icons displaying as long as the tracker URL itself has a favicon.ico. If the tracker itself's URL does not have a favicon,you'll need to go to the "real" tracker site and add /favicon.ico to save it, then you can have the tracker icon by itself on the farthest left to reference which tracker they belong to quickly!

I'm collecting tracker icons for those who find their tracker does not have them. You must go to the tracker's real site with /favicon.ico added. This must be resized to 16x16 and saved as a PNG file with zero compression. The filename must be the same as the one displayed in the Trackers list. So if it's "tracker.domain.com/announce" for the full tracker URL in 'edit trackers', your filename needs to be "domain.com.png" 16x16 and placed in your config folder (%APPDATA%/deluge/icons), and Deluge will need to be restarted.

Here is a bunch of mostly unidentified tracker icons. If you know the tracker is alive and want to help identify it, let me know which tracker it is and the row and column. The bottom left is 1x1, and the second from the left on the bottom is 1x2, so height x length. Would recommend you PM me this information, as I will need the main domain and TLD - as above, to convert It to .png with proper naming to be picked up by Deluge. If you have any questions about this, you can also PM me.

There will be quite a few trackers that don't have favicons, but we have them or can get them, so I'd like to make a pack for all of us to have complete icon sets for our trackers as seen in the picture below!



If you have any other questions, ideas/thoughts, start up a conversation!

[highvoltage]

great work, thank you very much

[razki4302]

deluge 2.2.0 is flagged with eset antivirus

[mhertz]

As my good friend highvoltage above, really appreciate your dedication and efforts bud, well besides severely pixxed off about the unjust OS outing slash mockering, and with that mean of-course honored for the mention. Anyway just a quick pad on back from me too, even though little late to party, sorry, and to be honest actually only learned of deluge 2.2.0 right now from your post lol, feel little embarrassed, but hey, not as involved as you I must admit. Again, or what called, much love bro, thanks for the contribution and will leave you to it, sure have your hands full.

[ambipro]

deluge 2.2.0 is flagged with eset antivirus

See this post.

viewtopic.php?t=57055

[ambipro]

I've just pushed updates for my Docker images. The images correspond as described below and will remain with the tags listed for the time being.

ghcr.io/zakkarry/deluge-develop-docker for the container image associated below

image tags for develop branch
master - develop branch (identified as 2.1.1-dev146) using libttorrent v2.0.11
libtorrentv1 - develop branch like above using libtorrent v1.2.20

image tags for 2.2.0
libtorrentv1-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 2.0.11
libtorrentv2-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 1.2.20

(previously did not checkout release tag properly, version should now show "2.2.0" without any post per Cas)

You can view all images at the packages page for my fork of LSIO here.

There still may be tracker which have not whitelisted 2.2.0 so check your trackers before you go and pull the latest version, some take time to validate.

Will be working on getting the binhex repo up to date as well, have not had the time to do so yet.

Also, GeoIP flags are automatically updated when ran if they have not been updated in the last week in these images, so your flags will always be up to date.