So with libtorrent 220.127.116.11 on windows, you can no longer redirect deluge to the new location of moved torrent files. I'm the maintainer of the FilebotTool plugin and this completely breaks its functionality.
windows 10 (tested on home and professional)
classic and daemon interface mode
Steps to reproduce:
- Create or add completed torrent.
- Using windows explorer or other program, move the completed torrent data (eg, move from downloads to movies folder)
- select torrent in deluge, right click, and select "move storage"
- select or type in new save location and hit ok
Expected Result: save location is changed, and a force re-check confirms correctness
Actual Result: path in torrent details remains unchanged, debug logs show `
Code: Select all
storage_moved_failed_alert: ... storage move failed: The system cannot move the file to a different disk drive
This was working in all previous builds of deluge, but it was just recently brought to my attention that it no longer works on deluge 1.3.13 for windows. As such, I don't currently know of a way to fix a moved torrent without removing and re-adding at the correct location.
apparently this behavior works as expected in qBitorrent which uses libtorrent 18.104.22.168. As this is a libtorrent issue, I'm not sure what can be done, but I wanted to bring it attention and see if anyone has any suggestions for a workaround.
I can provide debug logs on request.