This commit is contained in:
Jean-Francois Dockes 2014-06-10 17:40:20 +02:00
parent 8e4a270b0c
commit c9576209ee
2 changed files with 8 additions and 7 deletions

View File

@ -228,9 +228,9 @@ many distributions.</p>
testing), just use the appropriate Debian repository.</p>
<p><i>Except they're not at the moment (2014-05)...</i>. So here are
1.19.13 packages for Debian stable (Wheezy)
<a href="debian-stable/recoll_1.19.13-1_amd64.deb">amd64</a>
and <a href="debian-stable/recoll_1.19.13-1_i386.deb">i386</a>.
1.19.14 packages for Debian stable (Wheezy)
<a href="debian-stable/recoll_1.19.14-1_amd64.deb">amd64</a>
and <a href="debian-stable/recoll_1.19.14-1_i386.deb">i386</a>.
You can list the <a href="debian-stable">directory</a> for the
source package and other files (e.g. python-recoll .deb).</p>

View File

@ -63,7 +63,8 @@ Configuration</em> menu.</p>
<h2><a name="minor_releases">Minor releases at a glance</a></h2>
<ul>
<li>1.19.14 fixes two relatively minor but ennoying issues in indexing:
<li>1.19.14 fixes relatively minor but ennoying issues in
indexing, plus a few other glitches:
<ul>
<li>The use of a separate readonly Database object for querying
the index while indexing would trigger Xapian errors, (bad
@ -75,10 +76,10 @@ Configuration</em> menu.</p>
forking and executing the filter could block on a mutex, and
lead to a 20 mn timeout for the affected father process thread
(happened only in multithread mode).</li>
<li>Also a possible overflow of the filter stack. This could only
really happen in pathological situations (hand-crafted recursive
zip file...).</li>
</ul>
<li>Also a possible overflow of the filter stack. This could only
really happen in pathological situations (hand-crafted recursive
zip file...).</li>
</li>
<li>1.19.13 hopefully fixes the rare but longstanding multithread