You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some files in torrents that I downloaded (~decade ago) have names starting with a space.
I heard it's considered incorrect on some systems, but surely not on *n?x it isn't.
When I was on v2.x, the torrent worked fine.
After switching to 3.00, transmission-remote --torrent X --info shows Error: Please Verify Local Data! Piece #Y is corrupt.
After verifying, transmission-remote --torrent X --info-files shows files whose names start with a space without said space.
Obviously these files are marked as not downloaded ("Done: 0%"), since they can't be found on disk.
My hypothesis: there is a stray trim() or trimmed() somewhere and it's applied to the file name.
What is the issue?
Some files in torrents that I downloaded (~decade ago) have names starting with a space.
I heard it's considered incorrect on some systems, but surely not on *n?x it isn't.
When I was on v2.x, the torrent worked fine.
After switching to 3.00,
transmission-remote --torrent X --info
showsError: Please Verify Local Data! Piece #Y is corrupt
.After verifying,
transmission-remote --torrent X --info-files
shows files whose names start with a space without said space.Obviously these files are marked as not downloaded ("Done: 0%"), since they can't be found on disk.
My hypothesis: there is a stray
trim()
ortrimmed()
somewhere and it's applied to the file name.Which application of Transmission?
transmission-daemon
Which version of Transmission?
3.00 (bb6b5a0)
The text was updated successfully, but these errors were encountered: