-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 2.0.7 doesn't compile with Node.js 16 #4846
Comments
This is related to the npm packages that the cockpit UI uses. Now we don't don't build or test on arch linux, so the only thing I can recommend is to try and update your npm packages. Goto: 389-ds-base/src/cockpit/389-console/ and run "npm update" and try building again |
Alright. I changed it to
Log here: |
Yeah not sure what is wrong. Something about the libsass version is not working on Arch Linux. You could try taking the package.json/package-lock.json files from 2.0.6 and copying them to 2.0.7 source, then run "npm install" and try again. But for security reasons we can not downgrade our npm package versions, and upcoming version are going to be updated as well as we continue move to Patternfly 4. So I guess there could be more issues coming on Arch linux?? Are you even using the Cockpit plugin? If not, it can be disable in the specfile we ship with the server (if you are suing that specfile). |
Building older version of 389-ds-base also results in the same error. I suspect that it might be related to node v16.5.0. It only recently landed in rawhide, and for the releases we used v14. |
Yeah, we use |
That was a good hint! I'm now using node 14 and that works just fine! |
I'm reopening the issue because on Fedora rawhide build fails with too:
We need to bump npm package versions in |
@vashirov do you know if this problem still occurs with all the fixes in cockpit ? |
Issue Description
Version 2.0.7 fails to compile with presumably forgotten headers.
Package Version and Platform:
Steps to Reproduce
Steps to reproduce the behavior:
Log here:
build.txt
The text was updated successfully, but these errors were encountered: