Deluge Forum

Libtorrent 1.2.4 just released now - not yet been updated as news on libtorrent main or release page but I saw it in git commit log just now. Note you already have it if using my newest installers anyways, as I use the "release-candidate" RC branch already, but just to get the extra commit added that changes the version number string, so deluge's 'about > help' dialog will state libtorrent 1.2.4 instead of 1.2.3, then I just now rebuilded libtorrent/installers accordingly.

I have thought about it, and will just keep as is, with regards to using libtorrent RC branch in the installers. Many/most times the RC builds are more stable, because contains alot of bugfixes and at times other stuff/improvements also, but as said, stuff expected to break something usually is tested first in other experimental branch before going to RC branch, and RC branch usually, just like now, just is bumped to new release version after enough fixes have been submitted. Also, because qbittorrent does it and states if building from source then RC branch is recommended.

Note I rebuild when having time, or "feeling" for it, and if a commit added that fixes something in documentation or in the simulation test cases, then I don't bother, likewise if irrelevant for deluge, or otherwise unimportant/un-useful in general, so if checking git commit log yourself, and wondering if at a later time I possibly haven't rebuilded lately perhalps, then check what the actual commit is about and not just the date/title entry, which not always give the full picture and you need check code and files changed too.

Looks like they just added a big update for announce_to_all_trackers/tiers. I wasn't using either of those settings so I'm not sure that was related to my issue.

I think your approach is a solid one. We always have the previous versions of installer in the OneDrive version control if we need them.

Yes, I rebuilt libtorrent/installers earlier today when saw that commit. Good catch with that OneDrive version-control thing, didn't even knew that honestly, as never used OneDrive besides this project here.

Montaigne, I apologise, I dunno why I suddenly don't see some messages here, as always visits this forum using a key-combo(quick-mark) defined for this forums new-post page, so I don't know what's happening lately - only saw this because went back in thread, to again little more thoroughly google the exact error message Vander posted earlier and you backed up too, which I appreciate, thanks.

Now that this is a stable release, then not much I can do about it, sorry, except either use my previously posted previous stable libtorrent a couple posts previous, or continue with 1.1.x if wanted. You can also use a previous version of installer instead as Vander stated before - note I think you need be logged into OneDrive for that version control thing to not be blank, or atleast was like that when I briefly tested it earlier today for first time - pretty cool actually, as list 12 previous versions.

mhertz wrote:Montaigne, I apologise, I dunno why I suddenly don't see some messages here, as always visits this forum using a key-combo(quick-mark) defined for this forums new-post page, so I don't know what's happening lately - only saw this because went back in thread, to again little more thoroughly google the exact error message Vander posted earlier and you backed up too, which I appreciate, thanks.

Now that this is a stable release, then not much I can do about it, sorry, except either use my previously posted previous stable libtorrent a couple posts previous, or continue with 1.1.x if wanted. You can also use a previous version of installer instead as Vander stated before - note I think you need be logged into OneDrive for that version control thing to not be blank, or atleast was like that when I briefly tested it earlier today for first time - pretty cool actually, as list 12 previous versions.

No problem.
Thanks for the suggestions and all your work .

You're welcome, and I appreciate that

Not an installer issue at all, but any idea why the change download location file selector always forgets the last used location?
Previously it remembered, so was easier to move torrents added in pause to their right final location...

Sorry, no, I don't know anything about such unfortunetly, and can only suggest you to open a bug-ticket reporting the behaviour for best chance of getting it fixed/changed. Sorry couldn't be of help.

@mhertz
Thank you for the installer but can you please make a howto or tutorial on how to make/compile from scratch?

That has already been made by Cas in this ticket here: https://dev.deluge-torrent.org/ticket/3201

Also, doadin has made a repo with several batchfiles for building from source: Deluge, libtorrent, gvsbuild and openssl : https://github.com/doadin/DelugeBuildFromSource

If in doubt of any of the steps, then i'll gladly help you out If needing libtorrent building help, likewise

My installer btw is just that, though including additionally:

Cut down from around 500mb to 200'ish mb.
Not needing adding anything to your PATH system environment variable.
Patched exe's to be portable and to fix bug with daemons always opening console-window.
Fix bug not being able to start daemon from connection-manager.
Fix geoip and add new definitions and update code to find it in main deluge dir also.
Fix several other bugs.
Add missing debug-exe's for nssm service usage.
Build/include new'er libtorrents, fixed to now support https tracker-announcing.
Fixed localisation.
Add git-develop deluge edition.
Use newer python version.
Everything contained in single folder Including also latest openssl and needed msvc-runtime-files.
Fixed several showstopping errors with conflicting files from %windir%\system32.
Added extra theme-options and e.g. option for native title-bars.
Improve installer, e.g. regarding direct upgrading, fix a bug, find/kill running deluge* processes and portable mode etc.

That was most of it, from top of head.