Changing path without moving the files or re-adding the torrent.

[The-Sound]

Let me preface saying that I might be using move wrong.

I have the following folders (simplified for the sake of the issue) with both identical files:

Folder1/Movie.mkv
Folder2/Movie.mkv

A while ago, when I added the torrent I did: stig add Movie.torrent --path Folder1
That works flawlessly, now, from the TUI, I wanted to move it to Folder2, with the files being already copied in there.

From other transmission clients, I expected it to change just the path, and being able to verify later. But stig instead started moving and overwritting the files.

I have to point out that as we all know, transmission hates long file operations, so I couldn't check if it was just verifying from the beginning, but from disk usage and timestamp of the files, I would say it indeed replace half of them.

[rndusr]

I'm not sure I understand. If both Folder1/Movie.mkv and Folder2/Movie.mkv are identical, it shouldn't matter if one is overwritten with the other, right? You say that half of the files were replaced, so there must be more files than just Movie.mkv. Can you create an example directory with files and the corresponding torrents that allows me to reproduce the issue?

[The-Sound]

Yeah there's more than one file but as pointed out I made a simplified structure to illustrate the issue.

The issue with the overwritting, is that it takes time and it locks transmission, when I alrady moved the file(s) manually with another tools like rsync, cp or whatever other that could be faster than transmission.

To reproduce the issue, have 2 folders with same contents. Then tell stig to change path from one to the other. Instead of just changing path, it will start moving the files from one folder to the other.

Trying to expand, in transmission-remote-gtk there's this check that does this exact behaviour:

If I check the box, it will move the files, like stig, if I uncheck it, it won't, it will only change the path.

[rndusr]

It looks like this is caused by the "move" parameter documented here: https://github.com/transmission/transmission/blob/main/docs/rpc-spec.md#36-moving-a-torrent stig has this hardcoded to true: https://github.com/rndusr/stig/blob/master/stig/client/aiotransmission/api_torrent.py#L644 I guess we could add a --move-files flag to the move command.

[The-Sound]

That sounds alright, or keep the default behaviour and add the flag to not move fails and only change path, the one that sounds better for you and for stig.