December 01 - A few minor fixes including some more UPnP fixes and translation updates. I have also added a new option to the Bandwidth preferences which allows you to turn off rate limiting for protocol overhead. What this will do is effectively change Deluge's behaviour back to how it was with 0.5.
This might be the last release in the 1.0 series as we are preparing to branch 1.1 off for stabilization.
Check out our FAQ before you start asking questions.
Add an option to not include IP overhead in rate limiting (this is equivalent to how 0.5.x behaves)
GtkUI:
Display the proper downloaded value in the statistics tab
Windows:
Fix broken graphic in new release dialog
Changes 1.0.5:
GtkUI:
Increase the per-torrent stop share ratio max to 99999.0
Fix #528 make sure gtkui config file is written before exiting
Fix UDP tracker support
WebUI:
Javascript auto refresh for both templates.
Windows:
Fix #577 adding torrents by drag n' drop
Fix association in Vista
Fix WebUI launch
Debian:
SID packages now requires Boost 1.36
Ubuntu:
Jaunty packages are now provided
Changes 1.0.4:
Core:
Fix #560 force an int value for global max connections
Fix #545 use proper values in ratio calculation
Fix UPnP again..
GtkUI:
Fix #565 wait for the deluged process to start to prevent defunct processes
OS X:
Fix issues with gettext
Windows:
Fix starting on non-English versions of Windows
Changes 1.0.3:
Core:
Fix upnp - it should work on more routers now too
Fix issue where Deluge would send improper stats to the tracker after a
pause/resume.
Fix issue where fastresume files would be rejected when using FAT32. This
would cause the torrent to be rechecked on every startup.
Fix ip filtering
GtkUI:
Re-add the "Max Connections Per Second" option with a default setting of 20
WebUI:
Fix White template for Opera
Misc:
Deluge will now use a system libtorrent library if available.
The build system will no longer build libtorrent if a system library is
detected.
Changes 1.0.2:
Core:
Fix issue where torrents will not be properly added to the session
Changes 1.0.1:
Core:
Change the default max global upload slots to 4 instead of -1 since libtorrent
will automatically open more slots to meet the upload speed limit.
Fix display of tracker error messages
Fix add_torrent_url() to download the torrent file in a thread to prevent
the main thread from blocking and causing the daemon to freeze.
Removed the 'Maximum Connections Per Second' setting and replaced it with a
default setting of 20. This should alleviate speed issues some are experiencing.
Changed max half-open connections default limit to 8 on XP/2000 and 4 on Vista
Prevent being able to set file priorities for compactly allocated torrents as
it is not intended to work.
Fix freezing on start-up issues on systems that do not have a properly
configured localhost entry.
Change max connections default setting to 200
Fix issue with invalid bencoding from some trackers
Plenty of libtorrent updates that should improve core stability
GtkUI:
Improve performance of files tab by only updating when values change
Misc:
Fix #187 set a 5 second timer to save the config file after a config value
has been changed.
Fix #503 change the boost lib detection logic to first look for -mt and
if not available, fall back to regular boost lib (non-multithreaded)
I have a question. Why do you choice to use new setup.py way in 1.x? I like 0.5.x's setup.py a lot, which it has very short paths by install everything in ${prefix}/share/* rather than Python's very long path. Also, it's a lot easier to remember where to put plugins in ${prefix}/share/deluge/plugins for the multi-user.
I have a question. Why do you choice to use new setup.py way in 1.x? I like 0.5.x's setup.py a lot, which it has very short paths by install everything in ${prefix}/share/* rather than Python's very long path. Also, it's a lot easier to remember where to put plugins in ${prefix}/share/deluge/plugins for the multi-user.
Hmm, it appears that 'install' might not be doing an 'install_data'. Do this:
It works now with install_data target. Thanks. If it is going to be that way, maybe you need to update the README?
Well, 'install_data' should be a sub command of 'install', so I don't really understand why it's not being run properly. I'm not much of an expert with distutils/setuptools so maybe I need to do some more reading about it.
Deluge
