Created attachment 179058 [details]
textproc/py-elasticsearch-curator-py svn generated diff file for revision 1 of port
textproc/py-elasticsearch-curator-py depends on elasticsearch>=2.3.0,<3.0.0 in release 3.4.1.
The Python library expected for elasticsearch-curator-py is less than v3.0.0, but textproc/py-elasticsearch-py has been bumped to the version 5.x.x api which is not backwardly compatible.
Generated new V2.4.1 of the py-elasticsearch-py port, under bug #216249, and the attached diff file shows the changes for this port to use the new port for the v2.x.x API.
Confirmed working with textproc/elasticsearch2 (2.4.2) and textproc/py-elasticsearch2-py (2.4.1) without error.
Functional testing performed - worked as expected against 11.0-RELEASE-p7, openjdk8-8.112.16_3 and ports tree r431710.
Thank you for this.
Someone contacted me by email asking about this issue. I have emailed them and will now test it here.
Why choose elasticsearch2-py=2.4.1 ?
Are you sure 216248 is the correct Depend On port? Should it be 216249?
I think I now understand how this came about.
textproc/py-elasticsearch-py was upgraded from 2.4.0 to 5.x
However, many ports still need v2 to work with older versions of elastic search, specifically textproc/py-elasticsearch-curator-py
Once textproc/py-elasticsearch2-py is created by #216249 we can fix textproc/py-elasticsearch-curator-py to use it instead of textproc/py-elasticsearch-py.
We may need to create textproc/py-elasticsearch2-curator-py instead....
A "v3" (3.5.1 / 3.x.x) variant of curator maybe potentially a way to go forwards, as the 5.x.x branch is currently a work in progress.
Latest 3.x.x and 4.x.x (4.2.5) require ES < 3.0 despite the compatibility matrix on the front page of the GH page. See:
It looks like the v5.x.x branch when released maybe backwardly compatible but no confirmation yet.
Hope this explains approach with retaining stable 3.5.1 and spinning a new dependency for textproc/py-elasticsearch2-py.
Updated Dependency; Sorry, human error on the depends - while FreeBSD can multitask, it seems my ability is questionable...
The latest release of Curator does not support ESv5 yet, see my comment #5. I believe that a compatible version of Curator is in the pipeline but no eta.
Is there anything I can do in support of this being progressed to closure please?
Happy to switch this to a New Port, following the naming convention of ES1,2,latest...
Your guidance would be most welcomed!
I'm sorry, but my time is overloaded at present. I am unable to do anything immediately.
Curator version 5.2.0 support the 5.x branch of elastic search. Dependencies / Blocking assignment altered.
New Patch required to bring textproc/py-elasticsearch-curator-py up to the latest...
textproc/py-curator-py|textproc/py-elasticsearch-curator|2018-04-09|Follow existing Elasticsearch naming conventions
Is marked BROKEN in ports r508154.
No longer marked as broken.
Shall we close this PR as overtaken by events?