For someone who's not terribly familiar with Debian's packaging system and policies, can someone explain this? Is it saying you'll no longer be able to type
`apt-get install elasticsearch`
in future Debian releases? Or is this something else?
`apt-get install elasticsearch`
in future Debian releases? Or is this something else?
* In Debian Jessie, you can still install the Debian Elasticsearch package, but it will not receive security updates any longer.
* In future releases of Debian, this package will not be available in the main repo, but will still be available in the unstable or jessie-backports repos.
* Elasticsearch (the company) maintains its own Apt repositories where they will provide updated versions according to their support policies. If you add this repository to your Debian based systems you can install the (supported) Elasticsearch package with "apt-get install elasticsearch".
It is my opinion that you should not deploy the Debian ES package in a production setting. Use the vendor repo and save yourself a headache.
For what it's worth, I am currently running off the official packages at moderate scale (~30 machines all together) and have not yet had an issue with it, though it's certainly possible that one will arise and I will thereafter curse Elasticsearch forever.
In this particular case though, security updates are critical, so what other choice is there unless you want to package your own?
E: elasticsearch: file-in-usr-marked-as-conffile usr/lib/systemd/system/elasticsearch.service
E: elasticsearch: description-starts-with-package-name
W: elasticsearch: description-too-long
E: elasticsearch: extended-description-is-empty
W: elasticsearch: non-standard-dir-perm etc/elasticsearch/ 0750 != 0755
W: elasticsearch: executable-is-not-world-readable etc/elasticsearch/elasticsearch.yml 0750
W: elasticsearch: executable-is-not-world-readable etc/elasticsearch/logging.yml 0750
W: elasticsearch: non-standard-dir-perm etc/elasticsearch/scripts/ 0750 != 0755
E: elasticsearch: dir-or-file-in-var-run var/run/elasticsearch/
E: elasticsearch: postrm-contains-additional-updaterc.d-calls etc/init.d/elasticsearch
W: elasticsearch: script-in-etc-init.d-not-registered-via-update-rc.d etc/init.d/elasticsearch
W: elasticsearch: executable-not-elf-or-script etc/elasticsearch/elasticsearch.yml
W: elasticsearch: executable-not-elf-or-script etc/elasticsearch/logging.yml
W: elasticsearch: maintainer-script-calls-systemctl postinst:82
W: elasticsearch: maintainer-script-calls-systemctl postrm:72
W: elasticsearch: maintainer-script-calls-systemctl prerm:51
they think it's too insecure to include in stable.
Sure it's not that there are known problems, but security isn't a thing you have or don't have; it's a process. If your process for identifying and fixing security flaws is broken, that's insecure.
Yes you will, it's just an old version without security updates.
> but you will be able to get it in unstable
No you won't, Stretch is the current unstable and elasticsearch is going to be removed from it.
elasticsearch will continue to remain in unstable