Helmut Grohne writes:
> Package: recoll
> Version: 1.20.3-2
> Severity: important
> File: /usr/bin/recollindex
>
> "recollindex -c someconfdir some/path" used to index to index some/path.
> Since upgrading from 1.17.3-2 to 1.20.3-2 it indexes /tmp instead.
>
> It seems that the new version does not provide any means to index files
> outside /tmp. If this observation is wrong, please downgrade the
> severity of this bug.
>
> Helmut
The way to specify things to be indexed is to set the "topdirs" variable
inside someconfdir/recoll.conf. This can be set by editing the file or from
the indexing configuration section of the GUI.
What is the value of this variable inside 'someconfdir' in the above test ?
Furthermore, additional args have always been ignored by recollindex if
neither -i nor -e was set. I just checked that this was true of 1.17
Did you actually mean to type "-i some/path" in the above report ?
In this case, some/path still needs to be inside the indexed area.
I just also checked that this was already the case with 1.17
Test: recollindex 1.17.4, ~/projets is not in topdirs:
recollindex -c ~/.recoll -i ~/projets
Diagnostic in the log file:
:4:../index/fsindexer.cpp:168:FsIndexer::indexFiles: skipping
[/home/dockes/projets] (ntd)
(ntd means not in top dirs).
So, at this point, I am at a loss to explain what you could do with 1.17
that you can not do with 1.20...
Regards,
Jean-Francois Dockes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
