Bug 237374
| Summary: | [NEW PORT] textproc/kibana7: Browser based analytics and search interface to ElasticSearch | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | rlwestlund |
| Component: | Individual Port(s) | Assignee: | Greg Lewis <glewis> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | 000.fbsd, elastic, glewis, jbaggs2016, jonaspalm, metsuke, mzs_47, otis, rlwestlund, tcberner |
| Priority: | --- | Keywords: | feature |
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
| See Also: |
https://github.com/elastic/kibana/pull/27255 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237372 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244849 |
||
| Attachments: | |||
|
Description
rlwestlund
2019-04-19 01:13:40 UTC
Hi, I see you chaged the severity down to Affects Only Me... I set it to Affects Some People because I figured there must be other people that could use this, it's not a fluke bug or something. Is that field supposed to be a measure of only people that we *know* have been affected by it? Makes more sense in retrospect... I thought it was weird that we were supposed to try to estimate. (In reply to rlwestlund from comment #1) The best way to describe it is a 'scope of the issue', not a measure of usefulness or value. Technically its the 'Severity' field, which technically only applies to 'bugs', say, as opposed to feature requests. If you treat a 'new port' as a 'bug' (a proposed change), the only person affected is the reporter, or the maintainer (also usually the reporter) Hi, Thanks to @rlwestlund(and others) for the effort, I am planning to use this or ELK 6 in production with CBSD. A quick search and I came across this below issue on Github, not sure whether this is related. https://github.com/elastic/kibana/pull/27255 On similar note, I guess sysutils/logstash7 is not required(for EL7) and sysutils/logstash6 is compatible. Created attachment 209063 [details]
textproc/elasticsearch7 (version 7.4.2)
Hello all. I needed some features in the latest Elasticsearch (7.4.2) and ported it locally over the weekend. I see here Elasticsearch 7 was in the works but I prior version. My files for 7.4.2 are attached. (This port is based on the Darwin build.) I maintain the py-elasticsearch-dsl port, and will be uploading a version7 of it shortly. I will also be submitting to reversion the older port as py-elasticsearch-dsl6, to be in keeping with the versioning on other Elasticsearch related ports. I also noted, that elasticsearch5 was EOL earlier this year (see: https://www.elastic.co/support/eol) so it looks like the team will only need to maintain 2 or 3 versions at a time going forward. ...and now I see I opened the wrong window and attached my files to the wrong PR. PR 237372 contains shar for new port elasticsearch 7 - 7.4.2 with some fixes (plist and distfile) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237372 Created attachment 212303 [details]
shar to add kibana7 - 7.6.1
Create new port kibana7.
Only build tested with "poudriere testport". I do not use Kibana. Please somebody else have to run test it.
Created attachment 212304 [details]
patch to add kibana 7.6.1
Maybe it is better to do repocopy kibana6 to kibana7 and then patch it to 7.6.1
Created attachment 212305 [details]
poudriere testport build log success for 11.3-RELEASE
Created attachment 212315 [details]
shar to add kibana7 - 7.6.1
fixed version number in pkg-descr "Kibana 7.x is compatible with Elasticsearch 7.x"
FWIW, this worked for me with node10 (10.19.0). I haven't tried node12, and I'm wondering why the current shar has that as the dependency. Have you tried running it with node12? Note that building it doesn't really count since all that does is copy files around, you need to start it up to see if it will run or not :) (In reply to Greg Lewis from comment #12) You absolutely right. Kibana 7.6.1 has node 10.19.0 as a requirement. It is my mistake. Even if I posted about it a month ago https://lists.freebsd.org/pipermail/freebsd-elastic/2020-February/000525.html I will fix it soon and upload new shar + patch with node10 as a dependency. Created attachment 212348 [details]
kibana7 - 7.6.1, fix dependency to node10
Changed to RUN_DEPENDS= node10>=10.18.0:www/node10
Created attachment 212349 [details]
patch to add kibana 7.6.1
A commit references this bug: Author: glewis Date: Thu Mar 12 23:59:14 UTC 2020 New revision: 528323 URL: https://svnweb.freebsd.org/changeset/ports/528323 Log: Add a port of Kibana 7.x PR: 237374 Submitted by: Miroslav Lachman <000.fbsd@quip.cz> Changes: head/textproc/Makefile head/textproc/kibana7/ head/textproc/kibana7/Makefile head/textproc/kibana7/distinfo head/textproc/kibana7/pkg-descr Thanks! Port committed. Now we need beats7 :) ^Triage: Assign to committer that resolved |
