#2898: deluged-1.3.13/libtorrent-1.1.0 messes up torrent directory names
-----------------------+----------------------------
 Reporter:  edechamps  |      Owner:
     Type:  bug        |     Status:  new
 Priority:  minor      |  Milestone:  needs verified
Component:  Unknown    |    Version:  1.3.13
 Keywords:             |
-----------------------+----------------------------
 I've been using Deluge 1.3.12 with libtorrent 1.0.7 on Debian Sid for
 quite some time. Recently Debian Sid upgraded to Deluge 1.3.13 and
 libtorrent 1.1.0. When I restarted Deluge on my existing torrents, I
 noticed that the directory names on some of my torrents were badly messed
 up. Specifically, Deluge seemed to add spurious slashes in the middle of
 top-level torrent directory names at random for no apparent reason.

 For example, say that a torrent has the following top-level directory name
 (i.e. the name of the directory inside the torrent itself):

 "Foo - Bar - Baz"

 For no apparent reason, that name changed to the following when the new
 version of deluged/libtorrent loaded the torrent:

 "Foo/- Bar - Baz"

 Basically the name is corrupted - a space was replaced by a slash, and I
 ended up with a subdirectory. It seems like, for some reason, it's only
 spaces or dots that get replaced by slashes. This is *very* weird.

 Additional information:

 - Obviously this prevented the affected torrents from starting, since
 Deluge couldn't find the data using the wrong path.

 - This only happened on a small subset (around 2%) of my torrents. I
 couldn't determine why these torrents were affected but not others - it
 seemed random. There were plenty of unaffected torrents using similar
 naming schemes.

 - If I downgrade libtorrent to 1.0.9 (keeping deluged-1.3.13), the problem
 goes away. This seems to indicate a regression was introduced between
 libtorrent 1.0.9 and 1.1.0.

 - I cannot use the rename functionality to try to fix the problem - it
 behaves very erratically on these corrupted torrents and basically refuses
 to rename the directory, or even manages to somehow corrupt the torrent
 itself (e.g. bencode complaining that end-of-file was reached).

 - None of my torrents use the top-level original directory name from the
 original torrent. I always rename every torrent with a custom top-level
 directory name immediately after I add them. Maybe this has something to
 do with the issue.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2898>
Deluge <http://deluge-torrent.org/>
Deluge Project

-- 
You received this message because you are subscribed to the Google Groups 
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to