FS#67415 - [kibana] is incompatible with current nodejs package
Attached to Project:
Community Packages
Opened by Antoine P (Stargateur) - Monday, 27 July 2020, 13:03 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 December 2022, 02:54 GMT
Opened by Antoine P (Stargateur) - Monday, 27 July 2020, 13:03 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 December 2022, 02:54 GMT
|
Details
kibana depends on nodejs but it seem nodejs is too much up
to date for kibana.
See detail here https://stackoverflow.com/questions/62742307/unable-to-start-kibana |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 04 December 2022, 02:54 GMT
Reason for closing: None
Additional comments about closing: Was dropped to the AUR 2022-01-08
Sunday, 04 December 2022, 02:54 GMT
Reason for closing: None
Additional comments about closing: Was dropped to the AUR 2022-01-08
nevermind dubnium is already at 10.23, I don't get why kibana refuse biger minor version, open a bug report in kibana github https://github.com/elastic/kibana/issues/84266
look like the 8.0 https://github.com/elastic/kibana/blob/master/.node-version will update to erbium.
ugly fix: edit /usr/share/kibana/package.json and change the end
"engines": {
"node": "10.23.0"
}
I don't know if this is possible but I would create a patch simply remove the check and changing the node version by just adding >=
Basically, it does two things:
1. Do not remove the "NodeJS" binaries that Kibana is providing in the source package
2. Use that binary to start the Kibana instance
With this I'm back on track, but I totally understand that this might not be desirable to no longer depend on the regular "nodejs" package