Elasticsearch-{1.6.2,1.7.1} has just been released by upstream: https://www.elastic.co/blog/elasticsearch-1-7-1-and-1-6-2-released Among other issues, those are fixing a bug that can potentially lead to a data loss situation. I'm not attaching any files this time, since simply updating the version numbers should work. It might be a good idea to remove older ebuilds inf order to prevent installing a known-to-be-buggy version. Reproducible: Always
+*elasticsearch-1.7.1 (03 Aug 2015) +*elasticsearch-1.6.2 (03 Aug 2015) + + 03 Aug 2015; Tony Vroon <chainsaw@gentoo.org> -elasticsearch-1.6.1.ebuild, + +elasticsearch-1.6.2.ebuild, -elasticsearch-1.7.0.ebuild, + +elasticsearch-1.7.1.ebuild: + This fixes a data corruption bug, which means that all previous ebuilds are + withdrawn to enforce the upgrade. Ebuilds & research by Ferenc Erki, closes + bug #556222.