This was partially fixed in Ubuntu 12.04 LTS (desktop). Puch / Puill:
If you copy from a remote Ubuntu platform, then the timestamp is preserved. But if you copy too, then only some platforms honour the timestamp (otherwise it is set to 'now' by the receiving platform). Tested today with full patched Ubuntu 12.04.2 LTS desktop, server, and Ubuntu 13.04 desktop (all 64-bit): - Copying from 13.04 desktop to 12.04 desktop ( Ok ) - Copying from 13.04 desktop to 12.04 server ( timestamp replaced, with 'now' ) - Copying from 12.04 desktop to 13.04 desktop ( Ok ) - Copying from 12.04 desktop to 12.04 server ( Ok, but new directories have timestamp of 'now' ) This should be fixed, and be consistent. Either as default behaviour, or from SFTP config. file. -- 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
