Bug 634278

Summary:	app-misc/elasticsearch: please restore at least the newest version for old upstream branches
Product:	Gentoo Linux	Reporter:	Michał Górny <mgorny>
Component:	Current packages	Assignee:	Tomáš Mózes <hydrapolic>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michał Górny archtester

2017-10-14 21:13:19 UTC

It turns out that infra is still running ES-1. Given the complete incompatibility of everything with everything, lack of proper maintainer for our software and the fact that as soon as something tries to upgrade ES to a newer version we'd lose archives.g.o and packages.g.o, it'd be really nice to actually have an ebuild for the version we're still running and its basic tooling.

I suppose some users would also appreciate having other old branches for their production services and ability to try to upgrade safely. FWICS at least some upstreams are actively maintaining multiple branches for them.

Comment 1 Tomáš Mózes 2017-10-16 04:38:38 UTC

Which versions would you like to restore? Wouldn't it be better to export/import data into a newer 5.x server?

As far as I know, only the 2.4 series receive some updates (Elasticsearch 2.4.6 released July 25, 2017), the 5.x branches don't receive updates after a new branch is released. Thus I try to keep the latest version from the current and previous branch.

Comment 2 Michał Górny archtester

2017-10-16 05:39:20 UTC

Newest 1.x and 2.x. Feel free to help us with the upgrade but until then, I'd prefer if things weren't on the verge odd accidentally breaking.

Comment 3 Tomáš Mózes 2017-10-16 06:51:14 UTC

According to https://www.elastic.co/support/eol, 1.x has reached it's EOL and 2.x is to follow by 2018-02-28. Wouldn't be adding 2.x enough so that you can upgrade from 1.x to 2.x and them from 2.x to 5.x?

Comment 4 Michał Górny archtester

2017-10-16 07:29:04 UTC

I'd rather have something to revert to, in case something goes wrong. At least unless you can realistically promise it's guaranteed to be painless.

Comment 5 Tomáš Mózes 2017-10-16 07:33:15 UTC

(In reply to Michał Górny from comment #4)
> At least unless you can realistically promise it's guaranteed to be painless.

I suppose not even elastic can make such promises ;)

Comment 6 Tomáš Mózes 2018-01-08 07:00:21 UTC

Sorry I didn't get to this, but 1.x and 2.x are EOL and unsupported, sorry.