Deluge

I fixed py3.9 support some months ago, it's linked a few posts up

Btw, I went to the repo to report it after having fixed it, but saw it was already reported and same solution posted to fix source-code as I used myself, so nothing for me to post there. No new release neither, I just checked now.

Short and consice/to-the-point has unfortunetly never been my forte, seemingly/apparently lol, but anyways, i'm gad to hear it's working, and I learned something along the way to, so thank you yourself, and I appreciate your kind words, thanks mate!

Posting here(petersasi's thread), since bug-report of my project posted, - thanks for report, I'll look into it later, tomorrow I believe(I'll edit this post later with an update when having tested/fixed - btw, if you mean step 9 don't work initially/alone, then that is normal as nothing to package ...

Just wanted to add a little tidbit. For another time, then you actually only need to copy auth from daemon and into user's config, as ashmandias also stated previously. This will make e.g. 'deluge-console info' etc work, but however when running only 'deluge-console' so the ncrurses UI starts, then ...

Indeed, I was actually thinking to mention that specifically previously, but forgot completely, but you catched it :) It's not a config issue, but actually a deluge bug which i've reported also on bugtracker already. There is a fix for it in an unmerged PR by Lucas C on deluge's github, but you don'...

Sorry for my test:test useless additions again firstly. Second, you're pretty much on point, except always stop deluged and deluge-web, I.e nothing deluge running(GTKUI neither etc), before editing config files as often gets lost without. Edit, and then start and test it works. You only have to star...

Sorry and thanks for correction ashmandias. Funny thing is I always used to say that, e.g helped people here also years ago stating this, but then recently found out about hostlist.conf and thought I was wrong before lol :) (I thought auth of daemon matched hostlist of client I mean). Anyway came to...

Auth file is for defining users/pass for the daemon to authenticate with. You add stuff to hostlist.conf to use/match against said values in the auth, so auth is for daemon and hostlist.conf is for clients connecting to daemon, unless I'm mistaken. I agree the wiki misses a few points regarding this...

Btw, if wanting to manually backport the py3.8 compatibility and ngettext commits from deluge develop onto deluge 2.0.3, then here's two commands doing that: sudo find /usr -path *deluge/i18n/util.py -exec sed -i "s/names='ngettext'/names=['ngettext']/" {} \; sudo find /usr -path *deluge/l...

Nice :) If it was me that stated you should restart daemon(s) after editing conf(s), then sorry, sometimes state that by mistake, and meant with daemon(s) closed and start afterwards, as deluge reads conf on start and ignores afterwards and rewrites it's copy from memory into conf again at closing, ...