Bug#829078: Any word?

2016-11-18 Thread Hilko Bengen
* Emmanuel Bourg:

> Hi Logan,
>
> If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
> install the upstream package available on the download page [1]. The
> elasticsearch package maintained by Debian isn't ready for prime time
> yet and will probably not be part of the Stretch release.

As the person who did the initial packaging work, I second this.

While it might be nice to get the package in order, I do not feel that
it's worth it. At this point, Elasticsearch is a crippled open-core
product that can only be properly used if one pays to use non-free
plug-ins for basic features that ought to be part of the core in the
first place, i.e. authentication or the option of encrypting inter-node
communication.

It is unclear to me whether or not upstream considers the 1.7 release
still supported. From my previous interactions with them regarding
security fixes I got the sense that this is not the case. They are not
even interested in providing detailed information about CVE-worthy
security issues that may help wih backporing.

Cheers,
-Hilko



Bug#829078: Any word?

2016-11-18 Thread Emmanuel Bourg
Le 18/11/2016 à 20:44, Logan Schmidt a écrit :

> Is there any word on this? We are deploying Elasticsearch servers today
> and are getting the same YAML problem when trying to start the service.
> We are using Ubuntu 16.10 (64 bit). Could we try different distro level
> like 16.04? This is a Debian specific issue not to sure what course of
> action to take here.

Hi Logan,

If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
install the upstream package available on the download page [1]. The
elasticsearch package maintained by Debian isn't ready for prime time
yet and will probably not be part of the Stretch release.

Emmanuel Bourg

[1] https://www.elastic.co/downloads/elasticsearch



Bug#829078: Any word?

2016-11-18 Thread Logan Schmidt
 

Is there any word on this? We are deploying Elasticsearch servers today
and are getting the same YAML problem when trying to start the service.
We are using Ubuntu 16.10 (64 bit). Could we try different distro level
like 16.04? This is a Debian specific issue not to sure what course of
action to take here. 

Any help is appreciated. Thanks, 

-- 

Logan Schmidt / Chief Technology Officer
lschm...@realpeoplesratings.com / 262-278-0243 

Real Peoples Ratings 
www.realpeoplesratings.com [1] 

  

Links:
--
[1] http://www.realpeoplesratings.com/