Date: Fri, 15 Sep 2017 04:57:15 +0200 From: Mark Clarke <mark@jumpingbean.co.za> To: Eugene Grosbein <eugen@grosbein.net>, ports@freebsd.org Subject: Re: Kibana53 - Not suitable node version available? Message-ID: <66788a84-ce89-993e-f1b6-2d2887399a6f@jumpingbean.co.za> In-Reply-To: <59B90146.1020502@grosbein.net> References: <8d18af9c-2e03-af84-ea7b-0c4a2b38d812@jumpingbean.co.za> <59B90146.1020502@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the help. Not sure how ports got out of date. I have done several base system upgrades 10.3-11.1 maybe that did it and was trying out the subversion approach to updating ports. There is something I don't understand about the process :) Will figure it out. I deleted /usr/ports and used portsnap to fetch a new base set. Busy building node 8.5 kind regards On 13/09/2017 11:58, Eugene Grosbein wrote: > On 13.09.2017 16:29, Mark Clarke wrote: >> Hi all, >> >> I posted a comment on a bug report regarding kibana53 failure to start >> by default on 11.0 and 11.1. I installed Kibana53 with pkg. From the bug >> report it looks like node 8.2 or higher is required. The maintainer >> asked me to post here instead to follow up. Miroslav pointed out in his >> comment that it will work with node-8.3.0 but I cannot find this in >> port nor in pkg. I have upgaded my ports tree via svn and all I have is >> node, and node010. Node is version 8.1 which is not compatible. How do I >> get more recent node versions in my ports tree or in pkg? > www/node was upgraded from 8.3.0 to 8.4.0 almost a month ago. > You could remove your ports tree and fetch it again from official mirror > as your source is obviously stale. > > -- Mark Clarke 📱 +2711-781 8014 🌍 www.JumpingBean.co.za
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66788a84-ce89-993e-f1b6-2d2887399a6f>