https://bugs.kde.org/show_bug.cgi?id=366036
--- Comment #11 from Simon <freisi...@gmail.com> ---
So I just opened digikam for the first time after compiling it with
Maik's commit. It looks like digikam now detects the symlinks as
duplicates. This output was printed repeatedly while scanning for new items:
digikam.database: Recognized "*somefile*" as identical to item 56019
For testing I looked up which file has ID 56019 and changed a tag on it.
This change is then not visible in *somefile*. The same is true the
other way round. So digikam seems to recognize that these are the same
items but it does not do anything about it.
On 25/07/16 20:18, Thomas Reifenberger via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=366036
>
> --- Comment #10 from Thomas Reifenberger <tspam+bugs.kde....@rfnbrgr.de> ---
> Just FYI: At least on my machine (up-to-date ArchLinux), the darktable
> versions
> 1.6.7 up to 2.0.5 handle the scenario described above as expected (respect
> symlinks, create/update sidecar file next to symlink).
>
> (In reply to Maik Qualmann from comment #8)
>> Also Darktable created not a sidecar file and prints a exiv2 exception.
>>
>> Maik
--
You are receiving this mail because:
You are watching all bug changes.
