Enable cross-seed deletion/retention #82
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Cross-seeds are detected by torrents that share the same root path Cross-seed handling is enabled if the config `delete_data` is set to `True`. If no data is deleted the cross-seed is handled by another strategy. If `delete_data` is set to `True` torrents seeding the same data as a torrent marked for deletion will fail. If enabled, deletion is by defailt not propagated to the cross-seeded torrents, instead the torrent marked for removal is flagged as soft-remove, meaning that the torrent will be deleted but not the data. By changing the flag `remove_cross_seeds` in the strategy configuration to `all_trackers` or a list of tracker host names deletion will propagate to either all or the selected trackers. Torrents included in the proagation will also be deleted, even if not included by the filter. Support has been added to: * deluge * qBittorrent APIv2 * Transmission A new field has been added to `Torrent#base_path`
|
Good idea. Thanks for your contribution, and I will review it as soon as possible. By the way you can ignore the CI failure because the task |
jerrymakesjelly
force-pushed
the
master
branch
2 times, most recently
from
8d80058 to
2827697
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I've attached a pull request that in part enables cross-seed handling
(its not enabled for uTorrent).
Cross-seeds are detected by torrents that share the same root path
Cross-seed handling is enabled if the config
delete_datais set toTrue. If no data is deleted the cross-seed is handled by anotherstrategy. The reason for this behaviour is that if
delete_datais setto
Truetorrents seeding the same data as a torrent marked for deletionwill fail.
If enabled, deletion is by defailt not propagated to the cross-seeded
torrents, instead the torrent marked for removal is flagged as
soft-remove, meaning that the torrent will be deleted but not the
data.
By changing the flag
remove_cross_seedsin the strategyconfiguration to
all_trackersor a list of tracker host namesdeletion will propagate to either all or the selected
trackers. Torrents included in the proagation will also be deleted,
even if not included by the filter.
Support has been added to:
A new field has been added to
Torrent#base_pathI don't know if this is in the scope of the project but I needed these
changes my self.
TODO
Cheers