1.19.14 packaging and web pages

packaging/debian/buildppa.sh

@@ -4,10 +4,10 @@
 # For the kio: (and kdesdk?)
 # sudo apt-get install pkg-kde-tools  cdbs
 
-RCLVERS=1.19.13
+RCLVERS=1.19.14
 LENSVERS=1.19.10.3543
 SCOPEVERS=1.19.12
-PPAVERS=5
+PPAVERS=1
 
 # For the unity-scope debian directory
 RCLSRC=/home/dockes/projets/fulltext/recoll/src

packaging/debian/debian/changelog

@@ -1,3 +1,20 @@
+recoll (1.19.14-1~ppaPPAVERS~SERIES1) SERIES; urgency=low
+                
+  * 1.19.14 fixes two relatively minor but ennoying issues in indexing:
+
+   - The use of a separate readonly Database object for querying the index
+     while indexing would trigger Xapian errors, (bad block reads), and
+     subsequent up-to-date check failures (leading to unnecessary
+     reindexing). The jury is out as to the cause, but using the same
+     object for reading and writing seems to eliminate the problem.
+
+   - A spurious log message in the child process between 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).
+  
+ -- Jean-Francois Dockes <jf@dockes.org>  Sat, 07 Jun 2014 18:56:00 +0200
+
 recoll (1.19.13-1~ppaPPAVERS~SERIES1) SERIES; urgency=low
                 
   * 1.19.13 hopefully fixes the multithreaded indexing crashes and silences

website/BUGS.html

@@ -29,7 +29,7 @@
 later versions. Bugs listed in the topmost section may also exist in older
 versions.</i></p>
 
-<h2><a name="b_latest">recoll 1.19.13</a></h2>
+<h2><a name="b_latest">recoll 1.19.14</a></h2>
 <ul>
   <li>An off-by-one error causes an array overflow while handling too
     deeply embedded documents (more than 20-deep). This can mostly
@@ -70,6 +70,19 @@ versions.</i></p>
     recoll.</li>
 </ul>
 
+<h2><a name="b_1_19_13">recoll 1.19.13</a></h2>
+<ul>
+  <li>Child process could hang during the fork-exec interval and cause a
+    20 mn filter timeout.</li>
+  <li>The use of separate read/write Xapian Database objects could cause
+    errors while checking the up-to-date status of documents.</li>
+  <li>Doc category filter names displayed in combobox were incorrect
+    when the order#:name format was used.</li>
+  <li>Possible overflow of the filter stack in pathological
+    cases.</li>
+</ul>
+
+
 <h2><a name="b_1_19_12">recoll 1.19.12</a></h2>
 <ul>
   <li>For all 1.19 releases including 1.19.12, there have been reports

website/download.html

@@ -67,7 +67,7 @@ function showdiv(viewid)
 <div id="general">
 <h2><a name="general">General information</a></h2>
 
-<p>The current version is 1.19.13. <a href="release-1.19.html">Release
+<p>The current version is 1.19.14. <a href="release-1.19.html">Release
 notes</a>.</p>
 
 <p>The download page for Recoll 1.18 is <a href="download-1.18.html">still
@@ -117,12 +117,12 @@ is probably no necessity to upgrade anyway.</p>
 <div id="source">
 <h2><a name="source">Source</a></h2>
 
-<h3>Current release distribution: 1.19.13:</h3>
+<h3>Current release distribution: 1.19.14:</h3>
 <!-- Attention: source packages must remain here, not in a
 subdirectory, because of all the places they're referred from
 (package watches) -->
 
-<p><a href="recoll-1.19.13.tar.gz">recoll-1.19.13.tar.gz</a>. </p>
+<p><a href="recoll-1.19.14.tar.gz">recoll-1.19.14.tar.gz</a>. </p>
 <!--
 <h3>Snapshot</h3>
 <p>I sometimes release a source tarfile when I consider that the
@@ -196,6 +196,7 @@ branch for the current production version.</p>
 <h3>Older recoll releases:</h3>
 
 <p>
+<a href="recoll-1.19.13.tar.gz">1.19.13</a>. 
 <a href="recoll-1.19.12p1.tar.gz">1.19.12p1</a>. 
 <a href="recoll-1.19.9.tar.gz">1.19.9</a>. 
 <a href="recoll-1.18.2.tar.gz">1.18.2</a>. 
@@ -305,7 +306,7 @@ more (email me if you need one).</p>
   Source: <a
   href="mageia2/recoll-1.18.1-1.mga2.src.rpm">recoll-1.18.1-1.mga2.src.rpm</a>
   </p>
--->>
+-->
 
 </div> <!-- Packages -->
 

website/index.html.en

@@ -54,7 +54,7 @@
         <li><a href="features.html">Detailed features</a>.
       </ul>
       <p>The current <span class="application">Recoll</span> version is
-	<a href="download.html">1.19.13</a> 
+	<a href="download.html">1.19.14</a> 
 	(<a href="release-1.19.html">Release notes</a>,
         <a href="BUGS.html">known bugs</a>).</p>
 
@@ -92,6 +92,10 @@
       <div class="news">
       
       <dl>
+        <dt>2014-06-07</dt> <dd>Version 1.19.14 is out and fixes a
+          handful of minor-to-ennoying indexing glitches (see the 
+          <a href="release-1.19.html">Release notes</a>).</dd>
+
         <dt>2014-05-06</dt> <dd>Version 1.19.13 is out and hopefully
           fixes the remaining (rare) crashes of multithreaded
           indexing.</dd>

website/index.html.fr

@@ -49,7 +49,7 @@
       <p><span class="application">Recoll</span> est un logiciel libre
 	gratuit, dont le code source est disponible sous licence GPL.
 	La dernière version est 
-        <a class="important" href="download.html">1.19.13</a>
+        <a class="important" href="download.html">1.19.14</a>
 	(<a href="release-1.19.html">notes sur la version, en
 	anglais</a>)</p> 
 
@@ -102,10 +102,16 @@
 
       <h2>Nouvelles: </h2>
       <dl>
+        <dt>2014-06-07</dt> <dd>La version 1.19.14 corrige encore
+          quelques problèmes dans l'indexation (erreurs dans la
+          vérification que l'index est à jour pour un document,
+          possible arrêt de l'indexation pour 20mn dans certains cas
+          rares, et autres).</dd>
 
         <dt>2014-05-06</dt> <dd> Version 1.19.13. A de bonnes chances
           de corriger les problèmes résiduels de l'indexation
           concurrente (multithread).</dd>
+
         <dt>2014-04-02</dt> <dd> Version 1.19.12. C'est la même que la
           1.19.11 à part un paramètre pour la taille des attributs
           stockés, qui n'est utile que dans des cas très

website/release-1.19.html

@@ -63,6 +63,24 @@ 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:
+    <ul>
+      <li>The use of a separate readonly Database object for querying
+        the index while indexing would trigger Xapian errors, (bad
+        block reads), and subsequent up-to-date check failures
+        (leading to unnecessary reindexing). The jury is out as to the
+        cause, but using the same object for reading and writing seems
+        to eliminate the problem.</li>
+      <li>An unnecessary log message in the child process between
+        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>
+    </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
     indexing crashes, which I hope were actually due to the now
     corrected mismanagement of Xapian::Document objects. It also