From owner-freebsd-elastic@freebsd.org Wed Jul 17 18:16:45 2019 Return-Path: Delivered-To: freebsd-elastic@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D9811B2A7F for ; Wed, 17 Jul 2019 18:16:45 +0000 (UTC) (envelope-from SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 8CDDB8DBC0 for ; Wed, 17 Jul 2019 18:16:45 +0000 (UTC) (envelope-from SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz) Received: by mailman.nyi.freebsd.org (Postfix) id 8A565B2A7E; Wed, 17 Jul 2019 18:16:45 +0000 (UTC) Delivered-To: elastic@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 88FADB2A7D for ; Wed, 17 Jul 2019 18:16:45 +0000 (UTC) (envelope-from SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F7A38DBBE; Wed, 17 Jul 2019 18:16:45 +0000 (UTC) (envelope-from SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id D8E4228417; Wed, 17 Jul 2019 20:16:33 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 1CE8728416; Wed, 17 Jul 2019 20:16:33 +0200 (CEST) Subject: Re: Removal of www/node6 To: "Bradley T. Hughes" , elastic@FreeBSD.org References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Wed, 17 Jul 2019 20:16:32 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 8CDDB8DBC0 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FORGED_RECIPIENTS_FORWARDING(0.00)[]; FORWARDED(0.00)[elastic@mailman.nyi.freebsd.org]; TO_DN_SOME(0.00)[]; MX_GOOD(-0.01)[cached: elsa.codelab.cz]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.67)[-0.673,0]; FORGED_SENDER(0.00)[000.fbsd@quip.cz,SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz]; RCVD_NO_TLS_LAST(0.10)[]; IP_SCORE(-1.25)[ip: (0.68), ipnet: 2610:1c1:1::/48(-3.89), asn: 11403(-2.98), country: US(-0.05)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=uYLe=VO=quip.cz=000.fbsd@elsa.codelab.cz]; FORGED_RECIPIENTS(0.00)[bhughes@freebsd.org ..,freebsd-elastic@freebsd.org]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; RCVD_COUNT_FIVE(0.00)[6]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; FORGED_SENDER_FORWARDING(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-elastic@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Support of ElasticSearch-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2019 18:16:45 -0000 Bradley T. Hughes wrote on 2019/07/12 23:34: > Howdy! > > The www/node6 port expired at the end of April, and I am keen to remove > it. However, there are a couple of ports maintained by elastic@ that > depend on it: textproc/kibana5 and textproc/kibana5-search-guard. > > As far as I understood it, kibana 5.x is also EOL, and can also be > removed, correct? If so, I can create a review that include > textproc/kibana5* along with my removal of www/node6. How does that > sound? :) I am the original author of the port kibana5-search-guard. We are no longer using Kibana and Search Guard plugin. From my point of view it can be removed but I am not sure if somebody else is using it or not. Kind regards Miroslav Lachman