Opened 9 months ago
#3650 new bug
Deluge does not truncate files when it should
| Reported by: | Nick Koretsky | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | needs verified |
| Component: | Unknown | Version: | master |
| Keywords: | Cc: |
Description
Its actually two bugs, but they are related
- There is 2 files, B is larger than A, but its content is identical to A up to A size. If torrent is created using A, and then added to deluge pointing to B followed by force recheck, deluge will accept it as 100% complete, but will not truncate the file to A size. So now you have a file that has junk at the end, but deluge is happy with it and claims that everything is ok.
- This is how you actually end up with the files from first bug. You add a torrent with "Move Complete" location selected. But you didnt check that there is folder here with an exact same folder and file names as in a torrent you have just added. Deluge downloads new torrent, and in the move phase, it copies content of a new files into older ones, but doesnt truncate larger files.
P.S. This is on deluge 2.2.0 with libtorrent 2.0.8.0, i am not sure if this bug is related to deluge core itself or libtorrent
Note:
See TracTickets
for help on using tickets.


