Closed tsiegleauq closed 5 years ago
My guess is that this is because the unescape happens twice in that case: it's started with the escaped version, the listens to the changes, but the call to sync then uses a unescaped version of the filename.
λ systemd-escape --unescape $(systemd-escape --unescape $(systemd-escape grive-test))
grive/test
Please see https://github.com/vitalif/grive2/pull/244 for a potential fix
Detecting changes using
systemctl --user start grive-changes@$(systemd-escape google-drive).service
works. However, uploading them works not.systemctl --user status grive-changes@$(systemd-escape google-drive).service
Will inform you that:therefore, no changes are being made.
Reproduce:
mkdir ~/grive-test
cd ~/grive-test
grive -a
and do the usuall stuffsystemctl --user start grive-changes@$(systemd-escape grive-test).service
touch ~/grive-test/test-file.txt
systemctl --user status grive-changes@$(systemd-escape grive-test).service
will show the error.