question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error generating DEB with version 1.1.0

See original GitHub issue

What version of electron-installer-debian are you using? 1.1.0

What version of node and npm are you using? node -v v11.6.0 npm -v 6.5.0

What operating system are you using? Linux Mint 19.1 Tessa, having Ubuntu 18.04 as base.

Can you compile the example app successfully?

If not, paste here the output of the following commands:

$ git clone https://github.com/electron-userland/electron-installer-debian.git
$ cd electron-installer-debian/example
$ DEBUG='electron-installer-debian' npm run build

What did you do? Please include the configuration you are using for electron-installer-debian. In order to create a *.deb from my electron project, I executed the npm script calls, first yarn build then yarn deb64. My script setting is:

  "scripts": {
    "start": "electron .",
    "build": "electron-packager . app --platform linux --arch x64 --out dist/",
    "deb64": "electron-installer-debian --src dist/app-linux-x64/ --dest dist/installers/ --arch amd64"
  },

What did you expect to happen? I expected to get a *.deb file in dist/installers.

What actually happened? I got an error:

$ electron-installer-debian --src dist/app-linux-x64/ --dest dist/installers/ --arch amd64 Creating package (this may take a while) Error: Error creating contents of package: Error creating binary symlink: could not find the Electron app binary at “dist/app-linux-x64/administration”. You may need to re-bundle the app using Electron Packager’s “executableName” option. at err (/home/jean/Documents/NewProject/administration/node_modules/electron-installer-common/src/error.js:12:13) Error: Error creating contents of package: Error creating binary symlink: could not find the Electron app binary at "dist/app-linux-x64/administration". You may need to re-bundle the app using Electron Packager's "executableName" option.\n at err (/home/jean/Documents/NewProject/administration/node_modules/electron-installer-common/src/error.js:12:13) error Command failed with exit code 1.

So, the path dist/app-linux-x64/administration obviously does not exist. It should be asking for dist/app-linux-x64 instead. The project’s name is called "name": "administration",, so there might be a mix up in electron-installer-debian version 1.1.0.

I solved this matter by moving one version down to electron-installer-debian version 1.0.1. Now everything works perfectly. I get the *.deb file as expected.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:15 (5 by maintainers)

github_iconTop GitHub Comments

17reactions
nasiruddin-saiyedcommented, Apr 26, 2019

Yes, I see why:

"build": "electron-packager . app --platform linux --arch x64 --out dist/",

You’re specifying the Electron application name in the command line parameters (app) instead of letting Electron Packager infer it from the name field in package.json. electron-installer-debian infers the name in the same way.

So what exactly is the Electron Packager’s executableName option?

See the Electron Packager API docs. (A brief description is also available if you run $(npm bin)/electron-packager --help.)

After reading docs and on multiple failure, successfully builded by Keeping name in packaje.json and electron-packager . app <-- this app (electron app name ) and package.json name should be same case sensitive

Happy Coding!

5reactions
mran3commented, Sep 4, 2020
{
  "name": "forged-text",
...
  "config": {
    "forge": {
      "packagerConfig": {
        "name": "forged-text"
      }
....

Both names in packager config and main package info should be the same on your package.json if you are using electron-forge on debian.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Dpkg .deb file - Not a debian format - Ask Ubuntu
This error happens when your deb file is broken. Check if you have downloaded properly (use md5 or sha checksum). I just had...
Read more >
How to convert perl modules into deb packages?
I'd say the error message is pretty clear: you need to install mod_perl2 , or tell Perl where it's installed if you installed...
Read more >
Create deb with CPack (Linux) - OpenRTM-aist
If you turn on document build and execute "cpack" without "make doc", the following error occurs. CMake Error at /home/project directory/build/doc/cmake_install ...
Read more >
5.4. Manipulating Packages with dpkg - GitHub Pages
dpkg is the base command for handling Debian packages on the system. If you have .deb packages, it is dpkg that allows installation...
Read more >
Workaround for libssl issue on Ubuntu 22.04 - Unity Forum
Hi all. If when opening the editor on the new LTS 22.04 you get the error 'No useable version of libssl' it's due...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found