Follow-up Comment #7, bug #15959 (project mldonkey):
"It would be better if the second torrent-file got another local name instead
of overwriting the one thatäs allready in use."
I could reproduce the error using your good description, thanks.
Trying to fix this is not that easy, inside the .torrent file
is a hard-coded filename which is used by MLDonkey.
Renaming the .torrent file makes this out-of-sync.
Another idea was to put the .torrent into
torrents/downloads/<file_id>/file.torrent.
file_id as seen in files.ini is a SHA1 hash of the text content
of the torrent file. Your two .torrent files differ for example
that one .torrent has one file more inside so different file_id
values were produced.
This solution produces the problem that the built-in tracker will
get confused when asked for Dag Vag - Almanacka (1983).torrent:
./torrents/downloads/X34OR7VZKJDR3SL2QXT2BN2H2VXW4VYZ/Dag Vag - Almanacka
(1983).torrent
./torrents/downloads/CNJUFHE26BBFTAG3Y4CBWHMDF6AHTCMH/Dag Vag - Almanacka
(1983).torrent
This scenario will avoid overwriting a .torrent file in your case.
But the MLDonkey tracker will not know which file to use.
After thinking about it the easiest solution would be to disallow
starting a new BT download when the .torrent file has the same
name than a currently working download, or maybe even also
seeded torrents. As this does happen seldomly (otherwise more
users would have experienced your bug) and its easy to code
without unwanted side-effects I would code this unless you or
others have a better idea to fix this bug.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=15959>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
_______________________________________________
Mldonkey-bugs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/mldonkey-bugs
