https://bugs.kde.org/show_bug.cgi?id=397242
Igor Poboiko <igor.pobo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://commits.kde.org/bal
| |oo/7e5c005e6a3b563013e2ba8c
| |b9c8f1b282e6f7b2
Resolution|--- |FIXED
Version Fixed In| |5.52
Status|CONFIRMED |RESOLVED
--- Comment #3 from Igor Poboiko <igor.pobo...@gmail.com> ---
Git commit 7e5c005e6a3b563013e2ba8cb9c8f1b282e6f7b2 by Igor Poboiko.
Committed on 08/10/2018 at 22:10.
Pushed by poboiko into branch 'master'.
[balooctl] Fix "index" command with already indexed, but moved file
Summary:
If I move a file (while baloo was not running) and perform `balooctl index` on
new file
(so that document Id is not changed), it won't update the path of the file,
keeping the
invalid entry in index.
Explicitly tell Baloo that we want to update everything concerning this file.
FIXED-IN: 5.52
Test Plan:
1) `echo "hello world" >~/file1`
2) `balooctl stop`
3) `mv ~/file1 ~/file2`
4) `balooctl start && balooctl index ~/file2`
5) `balooshow file2` and `balooshow -x <DOCUMENT_ID_OF_FILE>`
The first command should show the right path, and the second command shouldn't
complain about bug in Baloo (invalid index entry)
Reviewers: #baloo, #frameworks, ngraham
Reviewed By: #baloo, ngraham
Subscribers: ngraham, kde-frameworks-devel
Tags: #frameworks, #baloo
Differential Revision: https://phabricator.kde.org/D15944
M +1 -1 src/tools/balooctl/indexer.cpp
https://commits.kde.org/baloo/7e5c005e6a3b563013e2ba8cb9c8f1b282e6f7b2
--
You are receiving this mail because:
You are watching all bug changes.
