Bug 241845 - sysutils/logstash6: update to 6.8.4
Summary: sysutils/logstash6: update to 6.8.4
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Greg Lewis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-09 21:20 UTC by Juraj Lutter
Modified: 2019-11-26 04:34 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (elastic)

Attachments
Update logstash6 to 6.8.4 (830 bytes, patch)
2019-11-09 21:20 UTC, Juraj Lutter 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juraj Lutter freebsd_committer freebsd_triage 2019-11-09 21:20:52 UTC 
Created attachment 209022 [details]
Update logstash6 to 6.8.4

See the diff attached.

Changes:
- Update logstash to 6.8.4
Comment 1 Juraj Lutter freebsd_committer freebsd_triage 2019-11-12 20:46:10 UTC 
If these ports are not actively maintained, I'd like to take the maintainership.
Comment 2 commit-hook freebsd_committer freebsd_triage 2019-11-23 15:24:00 UTC 
A commit references this bug:

Author: glewis
Date: Sat Nov 23 15:23:25 UTC 2019
New revision: 518246
URL: https://svnweb.freebsd.org/changeset/ports/518246

Log:
  Update to 6.8.4

  PR:		241845
  Submitted by:	Juraj Lutter <juraj@lutter.sk>

Changes:
  head/sysutils/logstash6/Makefile
  head/sysutils/logstash6/distinfo
Comment 3 Dan Langille freebsd_committer freebsd_triage 2019-11-23 15:36:46 UTC 
Do you have this working with TLS?

re https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241845
Comment 4 Greg Lewis freebsd_committer freebsd_triage 2019-11-23 16:28:53 UTC 
I haven't yet looked if this will require an update to the TLS patch or not
Comment 5 Greg Lewis freebsd_committer freebsd_triage 2019-11-23 16:30:19 UTC 
Juraj, would you prefer to reset the maintainer on all the ELK ports to yourself or just change elasticsearch6 to be elastic@?
Comment 6 Juraj Lutter freebsd_committer freebsd_triage 2019-11-23 16:34:39 UTC 
I do not really care :-) As long as I will be able to receive notifications.
Comment 7 Juraj Lutter freebsd_committer freebsd_triage 2019-11-23 16:35:42 UTC 
And regarding the TLS patch, I already opened it up to see what will be needed to bring it up to date for 6.8.4 and some reasonable OpenSSL version. Is OpenSSL from ports or from base preferred?
Comment 8 Greg Lewis freebsd_committer freebsd_triage 2019-11-23 17:22:51 UTC 
I preferred the one from base since that simplifies the dependencies.  I doubt that it will make a substantial difference, so simplicity was preferred.

Still looking to see if it works successfully though.

In terms of notifications, if you are subscribed to elastic@ then you will get notified if elastic@ is the maintainer.  The positive is that so will everyone else on the mailing list :)
Comment 9 Juraj Lutter freebsd_committer freebsd_triage 2019-11-23 17:55:31 UTC 
I subscribed to elastic@

And in the meantime, I also did my own update to 6.8.4 with TLS patch, looking at it.
Comment 10 Greg Lewis freebsd_committer freebsd_triage 2019-11-26 04:34:36 UTC 
I've switch elasticsearch6 to elastic@.  Thanks!