I also want to note this is a serius bug for timestamp related file synchronisation. (Multi node home directory synchronisation over secure SFTP)
Reproduce: SFTP already mounted in nautilus (automatic by gigolo) >cd ~;touch -d '1 May 2012 10:22' test.txt >stat test.txt >cp test.txt .gvfs/SFTP on <FQDN>/<PATH>/ >stat .gvfs/<FQDN>/<PATH>/test.tst all tme staps ar changed (normal behavior cp) >touch -d '1 May 2012 10:22' .gvfs/SFTP on <FQDN>/<PATH>/test.tst ---> ERROR: touch: setting times of `.gvfs/SFTP on <FQDN>/<PATH>/bug.txt': Operation not supported -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/332646 Title: sftp does not set timestamps Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs when copying or moving files to a directory mounted over sftp, the time stamps are not preserved. this affects both hardy and intrepid (in hardy, it was tested with a patched version of nautilus hence that version used to forget timestamps on copy anyway). in both cases, i tested it locally and everything was preserved as it should be. moreover, when moving, nautilus first displays the correct time stamp and only on refreshing shows the wrong updated one. as timestamps can be considered considered important information, i suggest this bug be treated as "losing data without notice". To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/332646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
