Kibana53 - Not suitable node version available?
Mark Clarke
mark at jumpingbean.co.za
Fri Sep 15 02:57:31 UTC 2017
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
More information about the freebsd-ports
mailing list