when renaming a virtual file, manage pin state for the target name

will avoid trying to set a pin state for a file that has just been
renamed by us

Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>

diff --git a/src/libsync/propagatorjobs.cpp b/src/libsync/propagatorjobs.cpp
index 112f16e9f882625ad0adff615a8d6827f2ad2dc8..5dc6a2430710d43103df01915ab2e4c10f96b22f 100644 (file)
--- a/src/libsync/propagatorjobs.cpp
+++ b/src/libsync/propagatorjobs.cpp
@@ -270,9 +270,9 @@ void PropagateLocalRename::start()
     }
 
     auto &vfs = propagator()->syncOptions()._vfs;
-    auto pinState = vfs->pinState(_item->_originalFile);
-    if (!vfs->setPinState(_item->_originalFile, PinState::Inherited)) {
-        qCWarning(lcPropagateLocalRename) << "Could not set pin state of" << _item->_originalFile << "to inherited";
+    auto pinState = vfs->pinState(_item->_renameTarget);
+    if (!vfs->setPinState(_item->_renameTarget, PinState::Inherited)) {
+        qCWarning(lcPropagateLocalRename) << "Could not set pin state of" << _item->_renameTarget << "to inherited";
     }
 
     const auto oldFile = _item->_file;