https://bugs.kde.org/show_bug.cgi?id=446715
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
See Also| |https://bugs.kde.org/show_b
| |ug.cgi?id=333678,
| |https://bugs.kde.org/show_b
| |ug.cgi?id=439438,
| |https://bugs.kde.org/show_b
| |ug.cgi?id=435383
--- Comment #1 from tagwer...@innerjoin.org ---
Yes, it's a constraint...
Or the constraint is that baloo works on the assumption that there's a
one-to-one mapping between the filename and the device number/inode. Meaning if
you have a filename, it can lookup an Id (based on the device number/inode); if
you have a device number/inode you can work back to what the indexed filename
was.
Symbolic links add an extra level of complexity.
See Bug 333678, Bug 439438 and also Bug 435383, scroll down to:
https://bugs.kde.org/show_bug.cgi?id=435383#c13
The latter gives a potential workround plus a "Don't do that" in the next
comment from the maintainer :-/
Confirming but I think it should be a duplicate of 333678...
--
You are receiving this mail because:
You are watching all bug changes.
