Bug 79937 - provide option for remote protocols to preserve permissions on copy
Summary: provide option for remote protocols to preserve permissions on copy
Status: RESOLVED DUPLICATE of bug 356651
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
Depends on:
Reported: 2004-04-19 09:42 UTC by Andy Parkins
Modified: 2018-04-24 21:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Andy Parkins 2004-04-19 09:42:49 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

Open two "file:" URLs in konqueror.
Drag a file from window A to window B.
File timestamp (and other attributes) have been preserved.

Open one "file:" URL and one "sftp:" or "fish:" URL
Draw a file from window A to window B.
File timestamp on destination has been overwritten with today's date.

I personally would prefer that the timestamp is preserved.  But at the very least these two cases should be consistent.  Either a copy preserves attributes or it doesn't.
Comment 1 Martin Bernreuther 2004-06-27 00:55:36 UTC
The same effect for SuSE 9.0/KDE 3.2.3 and also with "smb:"
I'll also prefer to have the timestamp preserved!!!
(even if cp will only do so using an option)
Comment 2 Matt Rogers 2004-12-16 16:44:26 UTC
using scp on the command line doesn't preserve permissions by default (you have to pass it an option to do so), so i see this as more of a wish for that functionality.
Comment 3 Djordje Nikolic 2005-07-13 10:32:09 UTC
*** This bug has been confirmed by popular vote. ***
Comment 4 Andy Parkins 2005-07-20 10:11:32 UTC
comment 2 says that this is a wish.  I disagree.  Either dragging from one window to another preserves timestamps or it doesn't - you can't have different behaviours based on what the protocol is.  The decision to preserve or not preserve is less important than consistency.
Comment 5 Andy Parkins 2005-09-09 14:11:26 UTC
This bug now seems to apply to the new media:/ kio-slave as well.  Copying from file:/home/user to file:/media/device preserves timestamps; copying from file:/home/user to media:/device does not.

I read in bug #56213 (which is exactly the same bug IMHO) that KIO doesn't support timestamp modification.  Is this the case?  Is it true that any file: to other: copy will alter the timestamps?
Comment 6 David Faure 2006-02-28 00:10:37 UTC
SVN commit 514315 by dfaure:

Preserve modification time when copying to other protocols too.
Currently implemented for file:/ -> system:/ and probably vice versa,
need to look at the other protocols.

CCBUG: 79937

 M  +9 -0      kio/forwardingslavebase.cpp  
 M  +17 -2     kio/job.cpp  
 M  +9 -0      kio/jobclasses.h  
 M  +18 -5     kio/slavebase.h  
 M  +102 -14   tests/jobtest.cpp  
 M  +7 -1      tests/jobtest.h  
Comment 7 Marco Menardi 2008-05-30 22:31:27 UTC
I've tested with fish and smb regarding timestamp. It works only one way. If I copy a file from remote to local, timestamp is preserved (so good!), while if I copy files from local to remote, they are create with current timestamp, losing the original one. Tried with both dolphin and konqueror, kde4.1beta. Please, fix the other way also.
Comment 8 Carlo Segato 2008-06-01 03:32:41 UTC
SVN commit 815042 by segato:

preserve the modification time when copying a file over the smb kioslave
it works only on systems with utime
CCBUG: 79937

 M  +4 -0      CMakeLists.txt  
 A             config-smb.h.cmake  
 M  +2 -0      kio_smb.h  
 M  +16 -0     kio_smb_file.cpp  

WebSVN link: http://websvn.kde.org/?view=rev&revision=815042
Comment 9 Nate Graham 2018-04-24 21:49:25 UTC

*** This bug has been marked as a duplicate of bug 356651 ***