Closed jgilfoil closed 5 years ago
I had similar mistake. She arise with processing torrent files which in deluge don't have "Mapped Files" property. i'm try fix this, but new path not correct - all file places at base patch in transmission.
Same issue here. I'm not sure how to set mapped_files in deluge.
I have the same problem. Is there a known workaround? In my case, it's all been on Linux with Deluge, and I'm trying to move to Transmission, and I get:
./BtMigrate --source Deluge --target Transmission --no-backup --verbose --dry-run [2019-Feb-09 13:43:56.796040] [I] Source: Deluge ("/home/sean/.config/deluge") [2019-Feb-09 13:43:56.796240] [I] Target: Transmission ("/home/sean/.config/transmission") [2019-Feb-09 13:43:56.796324] [D] [Deluge] Loading torrents.fastresume [2019-Feb-09 13:43:56.798957] [D] [Deluge] Loading torrents.state terminate called recursively terminate called recursively Aborted (core dumped)
Sadly I never found a work around. I ended up leaving my existing torrents on deluge and started fresh with transmission with new torrents going forward.
"mapped_files" key is now optional. That was the original intention, but I guess I need to start writing unit tests... Thanks everyone for reporting this.
So this is probably a bit of an edge case. I converted my uTorrent torrents from windows to deluge on windows. Than from deluge on windows to deluge on linux by modifying the paths with scripts (and that worked). Now i'm attempting to convert them from deluge to transmission but running into issues.
command used is:
The output is: