Bug 301025 - Unable to cross-seed
Summary: Unable to cross-seed
Status: CONFIRMED
Alias: None
Product: ktorrent
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
: 304570 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-06-02 03:22 UTC by Mike Vaughn
Modified: 2015-02-20 19:30 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Vaughn 2012-06-02 03:22:06 UTC
When attempting to cross-seed files to multiple trackers, I get this error message: "Opening the torrent ..., would share one or more files with the following torrents. Torrents are not allowed to write to the same files. Please select a different location." Cross-seeding has become a rather popular method for maintaining a good share ratio, especially on private trackers. Numerous other BT clients allow cross-seeding (including uTorrent, qBittorrent, and Deluge). Please add this ability to KTorrent.

Reproducible: Always

Steps to Reproduce:
1. Attempt to seed a torrent that contains the same files as another torrent you're seeding.
Comment 1 Joris Guisson 2012-08-05 09:06:21 UTC
*** Bug 304570 has been marked as a duplicate of this bug. ***
Comment 2 andy 2013-07-20 03:29:44 UTC
the checking seems to be making sense technically.  

practically in my parts of the world, it happens frequently.  the duplicated files are usually links to sponsor or advertising.  it thus caused some inconvenience.

when I deselect those duplicated files and the donwload does not duplicate, I still get the same message from KTorrent.  seems like a bug to me.

is it possible to simply download the duplicated files as e.g. file (1)?  thanks.
Comment 3 Marcus M 2015-01-14 21:24:34 UTC
How cat this be unconfirmed and still unresolved?! It is simple and very annoying bug. Please, fix this.
Comment 4 Marcus M 2015-02-20 19:15:26 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Marcus M 2015-02-20 19:30:16 UTC
It appears that there is a workaround for this issue. You have to select an empty (new) download directory for each newly added torrent, then move data from already downloaded torrent instance to that dir and then initiate "Check data" on newly added torrent - it will realize that all the data is already there and just start seeding.

You will have two separate entries for same data which is logical as there is two different "torrents" seeding to different private trackers (possibly exposing two different number of chunks and their size). It is not convenient but it works.

Someone should definitely work on this - maybe adding some sort of notification/message and generally allowing such scenarios.