If eupdatedb encounters an error it sends the error message to stdout instead of stderr. This is quite annoying if you have a cronjob for eupdatedb which redirects stdout to /dev/null as it will fail silently if an error occurs.
*** Bug 134315 has been marked as a duplicate of this bug. ***
Done in git: commit a722383b1b0902a86fb372d944775381763122b5 @https://github.com/fuzzyray/esearch/
Released in esearch-1.0