mtime is changed when copying over sftp

[walter44]

Binary package hint: nautilus

When copying files from a lokal system to a server via sftp on a ext3 filesystem, the modification date on the copy date is set. This is wrong, copy is not a change! The system we are useless for archiving. The error ist reproducible.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.26.2-0ubuntu2
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.28-13-generic i686

[Pedro Villavicencio (pedro)]

bug reports should be filed in english, please open a new one.

[walter44 (walter-gromek)]

Pedro Villavicencio schrieb:
> bug reports should be filed in english, please open a new one.
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Invalid
>
http://de.babelfish.yahoo.com/

vergiss es, ich hab eine deutsche version

--
Ing. Walter Gromek 2231 Strasshof, Parkstrasse 33
Tel: [phone] Fax: [phone]
<email address hidden> http://www.iggmp.net

Bankverbindung: IG-GMP Verein für Gartenbahnen mit Personenbeförderung
IBAN: AT75 19370 31010169005 BIC: DRESATWX

Diese E-Mail wurde auf Linux unter Zuhilfenahme eines freilaufenden
Pinguins in artgerechter Haltung erstellt.

[Ilya Barygin (randomaction)]

Translated description added.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[Sebastien Bacher (seb128)]

the issue is similar to bug #247980 which is fixed in recent versions

No need to translate for users, they need to write english description or to reply to comments there is already lot of bugs for the number of triagers no need to make efforts to reopen those not described in english where the submitter will not reply to comments

[Philip Muškovac (yofel)]

SFTP connections are handled by gvfs in gnome, so the bug should belong there I think. And yes, it's still not fixed like described in the upstream bug report about this.