-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Build failing with EEXIST: file already exists #3179
Comments
Set env |
Is it possible to provide project or sample to reproduce (locally you can reproduce using env |
Thanks for the reply @develar , Setting the env variable works 👍 I can't provide the project, its on a private repo, but I've made a quick sample app using the same dependencies as the app that has the problem https://github.com/smithalan92/electron-builder-sample-error-app
|
* Set env `USE_HARD_LINKS=false` to workaround electron-builder errors (electron-userland/electron-builder#3179) * Do not update github releases when a build failed * Increase no activity timeout to 40 mins for Docker build * Remove rpm from target package types * Update github releases for the master branch only
Make sure electron-rebuild pick a more up do date version of node-abi for electron >= 2 compatibility. Set env USE_HARD_LINKS=false as workaround. See electron-userland/electron-builder#3179 Changed linux package (libopenjp2-tools wasn't found). See https://github.com/electron-userland/electron-builder/releases/tag/v20.0.4
Make sure electron-rebuild pick a more up do date version of node-abi for electron >= 2 compatibility. Set env USE_HARD_LINKS=false as workaround. See electron-userland/electron-builder#3179 Changed linux package (libopenjp2-tools wasn't found). See https://github.com/electron-userland/electron-builder/releases/tag/v20.0.4
Make sure electron-rebuild pick a more up do date version of node-abi for electron >= 2 compatibility. Set env USE_HARD_LINKS=false as workaround. See electron-userland/electron-builder#3179 Changed linux package (libopenjp2-tools wasn't found). See https://github.com/electron-userland/electron-builder/releases/tag/v20.0.4
@smithalan92 @develar Where do you set the USE_HARD_LINKS env variable? I am also facing the same issue with electron-builder 20.43.0 while building on mac For now I created a file named electron-builder.env and put it in there. |
@snene For Windows it needs to be set in System Environment Variables, for MacOS it needs to go in your ~/.bashrc or ~/.bash_profile file ( see here |
Thanks a bunch for the prompt reply @smithalan92 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Finally, this seems to have fixed the problem. I'm recording my comment here in case it helps others in newer builds of |
Just ran into this issue on v22.13.1. |
Is there a long-term fix for this planned? |
Also happens (electron-builder 22.14.13) using a CUSTOM github actions runner, while I can build without errors on the same machine if I run electron-builder not through the github runner. I can confirm that adding I tested this in an environment where the output was an universal binary DMG. |
Ref: electron-userland/electron-builder#3179 Signed-off-by: Akos Kitta <a.kitta@arduino.cc>
I ran into this issue while I was building code on a macOS jenkins node. electron-builder version: Currently the source code of builder-util/src/fs.ts is thus electron-builder will enable _isUseHardLink on jenkins automatically, whereas it didn't work on my macOS jenkins node. |
20.26.0 ( latest )
MacOS - DMG , Windows - Squirrel ( Windows build passes, MacOS build fails)
I'm having the same issue as was brought up here #3039 , The MacOS build fails with EEXIST: file already exists, below is a sample of the error, there are more similar errors in the error log. This only happens on the CI (Bitrise) , if I run the build on a local machine it works perfectly, this also only seems to affect MacOS, Windows local & CI builds work perfectly.
The text was updated successfully, but these errors were encountered: