Home
December 21, 2018
https://trac.transmissionbt.com/ticket/6168#comment:1
Official trac and svn are a bit in disarray with a full or partial move to github pending. I will continue to monitor official (trac, svn, github, etc.) issues, changes and source for any pertinence to the 2.77 core and resolve such.
The best place to obtain up to date general support is
sourceforge discussion
The enhancements and usage there apply synonymously to all platforms
and specifically supersede what is presented in the direct github wiki.
The svn/trunk branch repository contains everything you need to compile Transmission. The libevent library (svn:external in upstream) is folded in using subtree merge. So just git-clone and you’re ready to build. If you plan to submit patches upstream please pay special attention when creating them so that they do not include any of the git specific files. You can download the repository here. For compiling under Windows cygwin use this. For Windows there are specific fixes and enhancements necessary, contrary to what you’ll read at the official Transmission website.
2.77 core
Official 2.9x branch remains as described below per 2.8×.
And for those reasons cfpp2p fork of transmission will not be utilizing
2.8x, 2.9x or higher.
Note that it was decided to maintain and compile the choice 2.7x core
rather than the somewhat buggy 2.8x core. That is why you will see
only infrequent and far less bug fixes than the official 2.8x branches.
Simply stated, 2.7x core is extremely stable and reliable. You won’t
have to worry about running it for extended days and having it quit
on you unexpectedly.
Well tested , 2.77 core and kept up to date
remote GUI
with latest updates
Bug fixes and enhancements through version 2.77+ (core) and 2.9x+ (trunk, except rename).
2.9x+ issues
2.9x+ pulls
The included remote GUI port is fine tuned to the daemon.
How to compile the enhanced remote GUI
How to compile MAC daemon and remote GUI
It is highly recommended to replace the web client files with those of cfpp2p transmission enhanced web client
It is recommended that Mac users compile the daemon and remote GUI
There is an older pre-compiled Mac native version from transmission ticket 532. Download via the link at comment 221
Native compile mirror is here
The Mac remote GUI
For Windows users you will find the most recent executables on Sourceforge.
Mirrors are here:
32 bit transmission daemon
64 bit transmission daemon
32 bit trs-D-112418
64 bit trsD64-112418
Mac remote GUI
web-client-32bit-and-64bit
and the Releases
November 12, 2014 The best place to obtain up to date general support is
sourceforge discussion
The enhancements and usage there apply synonymously to all platforms
and specifically supersede what is presented in the direct github wiki.
Historical TurboT wiki is here.
December 28, 2012
And now in the master branch is a customized web client for this temporary PIECE fork version of transmission. Download the repository files here and replace the installed web-client files with those.
In the inspector’s files pane of the advanced or experimental view you can toggle the download state of the torrent’s files.
This can also be done in the shift Admin view.
All bug fixes currently in transmission trunk are included.
All tickets closed by release 2.74
All tickets closed by release 2.75
Also included, among several others, are many additional bug fixes and enhancements not limited to:
Prefetching of magnetized metadata right away
Improve “No Data Found” error message and recovery behavior
Make it possible to choose what files to download after getting magnet metadata
Seeding progress bars do not show in Web UI
The correct implementation of Blocklists loaded in Transmission should be used to filter DHT communication
and of course
Collect unwanted, but received, blocks in a separate file
With extreme care you can also toggle to a verify state from the “Normal View” of the customized web client.
Use this only when you know exactly what you are doing!
Use this only when you know exactly what you are doing!
Take this warning seriously.
Since the piece data itself is not checked against the checksums
in the torrent, using this function with partially complete files
will result in bad data being sent to peers. This is not what you want.
Take extra care when using this function, or just don’t use ‘Skip Verify’
