Arch Linux

red-lichtie

Member

Registered: 2015-03-08

Posts: 53

rancher-desktop 1.8.1-1 fails build

Package rancher-desktop gets to packaging stage and fails due to a missing file "dist/app/background.js".

What can I do to build and upgrade this package?

Here is the output at the end of the build:

> rancher-desktop@1.8.1 package
> node scripts/ts-wrapper.js scripts/package.ts

Packaging...
  • electron-builder  version=23.6.0 os=6.2.8-arch1-1
  • loaded configuration  file=$HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/electron-builder.yml
  • description is missed in the package.json  appPackageFile=$HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/package.json
  • writing effective config  file=dist/builder-effective-config.yaml
  • rebuilding native dependencies  dependencies=bufferutil@4.0.7, ffi-napi@4.0.3, native-reg@1.1.1, ref-napi@3.0.3, utf-8-validate@5.0.9 platform=linux arch=x64
  • packaging       platform=linux arch=x64 electron=20.3.8 appOutDir=dist/linux-unpacked
  ⨯ Application entry file "dist/app/background.js" in the "$HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/dist/linux-unpacked/resources/app.asar" does not exist. Seems like a wrong configuration.  failedTask=build stackTrace=Error: Application entry file "dist/app/background.js" in the "$HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/dist/linux-unpacked/resources/app.asar" does not exist. Seems like a wrong configuration.
    at error ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/asar/asarFileChecker.ts:7:12)
    at Object.checkFileInArchive ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/asar/asarFileChecker.ts:31:11)
    at LinuxPackager.checkFileInPackage ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/platformPackager.ts:503:7)
    at LinuxPackager.sanityCheckPackage ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/platformPackager.ts:551:5)
    at LinuxPackager.doPack ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/platformPackager.ts:312:5)
    at LinuxPackager.pack ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/platformPackager.ts:136:5)
    at Packager.doBuild ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/packager.ts:441:9)
    at Object.executeFinally ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/builder-util/src/promise.ts:12:14)
    at Packager._build ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/packager.ts:376:31)
    at Packager.build ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/app-builder-lib/src/packager.ts:337:12)
    at Object.executeFinally ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/node_modules/builder-util/src/promise.ts:12:14)
Error: node exited with code 1
    at ChildProcess.<anonymous> ($HOME/.cache/yay/rancher-desktop/src/rancher-desktop-1.8.1/pkg/rancher-desktop/utils/childProcess.ts:245:33)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:489:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12) {
  code: 1,
  command: [
    'node',
    'node_modules/electron-builder/out/cli/cli.js',
    '-c.extraMetadata.version=1.8.1'
  ]
}
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: rancher-desktop-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
rancher-desktop - exit status 4

---

Doing it the Linux way since 1997 and Arch way since 2015 (and loving it!)
Platforms: Intel, ARMv6 (Raspberry Pi), ARMv7 (BeagleBone Black), ARMv8 (Raspberry Pi)
Languages: C, C++, ASM, Pascal & Java

Stefan Husmann

Member

From: Germany

Registered: 2007-08-07

Posts: 1,391

Re: rancher-desktop 1.8.1-1 fails build

Packaging electron apps can be a mess. Ask the AUR maintainer or use the upstream-provided binary.