https://bugs.kde.org/show_bug.cgi?id=427183
--- Comment #2 from a...@disroot.org --- (In reply to Maik Qualmann from comment #1) > I understand correctly that digiKam only sees a 0-byte file via the symlink? Yes, that is correct: git-annex replaces the files with (0-byte) symlinks and allows for a smart way to handle the deletion of parts of the repo. > Well, then it is clear that when the scan for new items at start runs, it > will re-scan these 0-byte images and generate an empty thumbnail. So it is intended that the (correct, old) thumbnails get overwritten with an empty thumbnail? > We could certainly ignore 0-byte files when scanning, but Exiv2 would no > longer display any metadata either. Just for my understanding: the Exiv2-metadata is not stored in a database but read again each time? > There would be a lot more problems with digiKam in normal operation with > 0-byte images. Hmmm... out of curiosity: do you have any other solution to my problem? I assume that my situation is not that uncommon: I have more images than my laptop can handle, so I have stored all them remotely (nfs or external hdd) and only parts of them locally. But I want digiKam to not forget what it had already seen (especially the folder structure, the metadata and the thumbnails). Is there a good solution? I thought git-annex is probably the smartest one, but I'm open to alternatives. -- You are receiving this mail because: You are watching all bug changes.
