-
Notifications
You must be signed in to change notification settings - Fork 150
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
Trying to build headlamp for openSUSE: conflict with plugin react #1934
Comments
Hmm, not sure. I don't think I have hit that before. |
And thanks for packaging Headlamp for OpenSUSE BTW. I couldn't be much of a help with this issue but if you run into more problems, keep opening issues so we make sure we make it easy for folks to build Headlamp in environments we likely haven't tested. |
Thanks for the reply! Which solution do you mean? There are many many comments recommending different things... Running |
Oh. It is tested using npm, not yarn. Is it possible for you to use npm? |
Hmm, that seems to have done the trick. At least that error is gone. Now I got some more errors:
Those errors are apparently not fatal, the build however fails here:
|
hrmm. That looks like dns failed. I wonder if it was a temporary network error? |
Did I forget to mention, the builds happen offline. So there is no network connectivity. I need to prepare everything beforehand. In this case I run What does npm want to do in that step? Does it need additional files? |
oh, ok. The make frontend does an npm install, which does network calls even when it has a node_modules. It sounds like you do the npm install with network connectivity, then keep the node_modules folder? Did you try “npm run build” instead of “make frontend”? I don’t think that requires the network. |
Good call @illume , I hadn't realized @johanneskastl was trying with yarn. @johanneskastl , about the offline build. Our initial flatpak build was also building offline (now we just use the already built binaries) and I had to use some tools that basically downloaded all the dependencies into a cache and then had to pass some arguments to make npm use that cache. Maybe this hint helps. |
@joaquimrocha Any hints on what you had to cache back then? Is there any documentation on what you did? I had a look at other openSUSE packages containing npm things, that is how I came up with using yarn to prepare that offline source. But as it seems to not properly dedupe and the build fails with the conflict, I am stuck between a rock and a hard place... |
@johanneskastl , you can check how I was building the flatpak at that version: This script would use the flatpak tool flatpak_node_generator to create fetch the tarballs related to headlamp's app/package-lock.json and frontend/package-lock.json, and create a cache structure that npm recognized. Like I said, I ran into problems with this and decided to just use Headlamp's already built binaries instead. I know very well this is not how Linux packages are built, usually. Probably there are other node-based tools that are packaged in RPM from distro maintainers, from which you can check what they are doing? |
Thanks @joaquimrocha I'll have a look. And yes, there are some other tools being package, that is where I got the yarn idea from. :-) |
Hi @johanneskastl . Were you able to progress on this? |
Thanks for asking, @joaquimrocha I did get a little further but was being stalled by other work. I think we can close this issue, as the original issue is solved. |
I am trying to package headlamp for openSUSE. I have successfully prepared everything for the offline build, but the frontend build is breaking:
Any idea why that might be?
The text was updated successfully, but these errors were encountered: