Version: unspecified (using KDE 4.6.5) OS: Linux I like to keep modification dates unchanged. I also use exif orientation changes and rsync which checks for file size and modification date differences. After the first meta-data change (when digikiam adds some digikam version to the metadata) future exif orientation changes do not change the files size. If modification time changes are also disabled then rsync sees no change in the file (without enabling full checksumming, and who wants to do that?) It would be kind of spiffy if digikam could check this, notice the unchanged file size and time and add a single byte of padding somewhere. Maybe if the padding gets absurd it could eventually wrap back to zero, but that's probably not even an issue practically. OK it's a self-inflicted corner case, and probably very egocentric, but that's my funny wish. ;) Reproducible: Always Steps to Reproduce: -unselect update filetimestamp when metadata are saved -change exif orientation once -rsync the file to somewhere (works fine if the file was never previously modified by digikim) -change exif orientation again -rsync again, does not detect the change and does not transfer the file. Expected Results: I fully expect the present results. But I'd like the second rsync to work.
Configure digiKam to update time-stamp for each changes on your files. rsync will detect changes and synchronize repositories. Also take a care about how you use rsync options. Gilles Caulier
That's fine, and completely understood if this request is just too particular , but the point was to be able to NOT change the time-stamp. I knew already how to do it by changing the time-stamps.
The option in metadata setup panel to handle time-stamp of file is the right option to use : "Update file timestamp when files are modified" You must turn off this option to fix your problem. Gilles Caulier