@ttrrev electron-builder made a breaking change in the config. should be fixed now
Search Criteria
Package Details: vesktop 1.5.5-5
Package Actions
Git Clone URL: | https://aur.archlinux.org/vesktop.git (read-only, click to copy) |
---|---|
Package Base: | vesktop |
Description: | A standalone Electron-based Discord app with Vencord & improved Linux support |
Upstream URL: | https://github.com/Vencord/Vesktop |
Keywords: | discord vencord vesktop |
Licenses: | GPL-3.0-only |
Conflicts: | vesktop |
Provides: | vesktop |
Submitter: | picokan |
Maintainer: | Edu4rdSHL (Covkie, zt64) |
Last Packager: | Covkie |
Votes: | 51 |
Popularity: | 7.60 |
First Submitted: | 2024-01-16 08:05 (UTC) |
Last Updated: | 2025-04-01 22:24 (UTC) |
Dependencies (6)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR)
- nss (nss-hgAUR)
- pnpm (yarn-pnpm-corepackAUR, corepackerAUR, pnpm-binAUR) (make)
- libnotify (libnotify-gitAUR) (optional) – Notifications
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (optional) – Open links, files, etc
Required by (3)
Sources (4)
Covkie commented on 2025-04-02 02:31 (UTC)
ttrrev commented on 2025-03-30 22:22 (UTC)
Trying to install vesktop via yay
but I get an error related to electron-builder. Any hints?
==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:38 2025)
==> Retrieving sources...
-> Found Vesktop-1.5.5.tar.gz
-> Found vesktop.desktop
-> Found vesktop.sh
-> Found afterPack.js
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
Vesktop-1.5.5.tar.gz ... Passed
vesktop.desktop ... Passed
vesktop.sh ... Passed
afterPack.js ... Passed
:: (1/1) Parsing SRCINFO: vesktop
==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:40 2025)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Vesktop-1.5.5.tar.gz
-> Found vesktop.desktop
-> Found vesktop.sh
-> Found afterPack.js
==> Validating source files with sha256sums...
Vesktop-1.5.5.tar.gz ... Passed
vesktop.desktop ... Passed
vesktop.sh ... Passed
afterPack.js ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Sources are ready.
==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:45 2025)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
> vesktop@1.5.5 build /home/trev/.cache/yay/vesktop/src/Vesktop-1.5.5
> tsx scripts/build/build.mts
• electron-builder version=26.0.12 os=6.13.8-zen1-1-zen
• loaded configuration file=package.json ("build" field)
⨯ Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema.
- configuration.linux should be one of these:
object { appId?, artifactName?, asar?, asarUnpack?, category?, compression?, cscKeyPassword?, cscLink?, defaultArch?, description?, desktop?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableArgs?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, maintainer?, mimeTypes?, packageCategory?, protocols?, publish?, releaseInfo?, synopsis?, target?, vendor? } | null
failedTask=build stackTrace=ValidationError: Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema.
- configuration.linux should be one of these:
object { appId?, artifactName?, asar?, asarUnpack?, category?, compression?, cscKeyPassword?, cscLink?, defaultArch?, description?, desktop?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableArgs?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, maintainer?, mimeTypes?, packageCategory?, protocols?, publish?, releaseInfo?, synopsis?, target?, vendor? } | null
at validate (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/@develar+schema-utils@2.6.5/node_modules/@develar/schema-utils/dist/validate.js:86:11)
at validateConfiguration (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/util/config/config.ts:239:3)
at Packager.validateConfig (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/packager.ts:384:5)
at Packager.build (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/packager.ts:392:5)
at executeFinally (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/builder-util@26.0.11/node_modules/builder-util/src/promise.ts:12:14)
==> ERROR: A failure occurred in build().
ninetailedtori commented on 2025-03-29 22:02 (UTC)
Seems to be a corepack issue with pnpm, see: https://github.com/nodejs/corepack/issues/616, https://github.com/nodejs/corepack/issues/612.
SwirlyStone5877 commented on 2025-03-08 02:29 (UTC) (edited on 2025-03-08 02:29 (UTC) by SwirlyStone5877)
@Edu4rdSHL: Does it work if using
makepkg
directly?
No, as that is what i was using when I got the same error.
Tried using yay
as well, and that didn't work either (I don't know why I tried, but it was nice to see anyway).
tetrachromat commented on 2025-03-07 23:01 (UTC)
fyi- if vesktop.sh
is going to use /bin/sh
, it should be POSIX-compliant. The [[
syntax for tests is a bashism. I am using dash as my /bin/sh
, and just noticed that vesktop is silently throwing an error on every startup.
I would recommend adjusting the script to use a single [
(looks like that will still work portably!), or failing that, you can specify that you want /bin/bash
in your shebang.
Edu4rdSHL commented on 2025-03-07 00:36 (UTC)
Does it work if using makepkg
directly?
SwirlyStone5877 commented on 2025-03-07 00:25 (UTC)
Unfortunately, the problem what @itlis pointed out occurs when installing manually without the use of pamac as well.
==> Making package: vesktop 1.5.5-4 (Thu 06 Mar 2025 06:17:21 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Vesktop-1.5.5.tar.gz
-> Found vesktop.desktop
-> Found vesktop.sh
-> Found afterPack.js
==> Validating source files with sha256sums...
Vesktop-1.5.5.tar.gz ... Passed
vesktop.desktop ... Passed
vesktop.sh ... Passed
afterPack.js ... Passed
==> Extracting sources...
-> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
if (key == null || signature == null) throw new Error(`Cannot find matching keyid: ${JSON.stringify({ signatures, keys })}`);
^
Error: Cannot find matching keyid: {"signatures":[{"sig":"MEUCIQD4HgoU3gpD1VhZl66ZKcKEjoK5+najimL8eN5vXJQQAwIgA3wqaVibkcwBu4ep9EF70MchM0G+Z3FxlMsgj+4UaJo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg=="}]}
at verifySignature (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
at fetchLatestStableVersion (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async fetchLatestStableVersion2 (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
at async Engine.getDefaultVersion (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
at async Engine.executePackageManagerRequest (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
at async Object.runMain (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23102:5)
Node.js v22.13.0
==> ERROR: A failure occurred in build().
Aborting...
Nothing else is helping. I am unable to use Vesktop as of now (except for the tar.gz version on it's GitHub releases page). This is great. Sooooo great.
itlis commented on 2025-02-16 12:40 (UTC) (edited on 2025-02-16 12:41 (UTC) by itlis)
Hi. I'm trying to install vesktop via "pamac install vesktop" but getting "Error: Cannot find matching keyid". Can someone help with it or at least explain what might be wrong? Full output (what looks like keys or ids removed to prevent leaks):
Building vesktop...
==> Making package: vesktop 1.5.5-4 (Sun 16 Feb 2025 15:31:35)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Vesktop-1.5.5.tar.gz
-> Found vesktop.desktop
-> Found vesktop.sh
-> Found afterPack.js
==> Validating source files with sha256sums...
Vesktop-1.5.5.tar.gz ... Passed
vesktop.desktop ... Passed
vesktop.sh ... Passed
afterPack.js ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
if (key == null || signature == null) throw new Error(`Cannot find matching keyid: ${JSON.stringify({ signatures, keys })}`);
^
Error: Cannot find matching keyid: {"signatures":[{"sig":"---","keyid":"SHA256:---"}],"keys":[{"expires":null,"keyid":"SHA256:---","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"---"}]}
at verifySignature (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
at fetchLatestStableVersion (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async fetchLatestStableVersion2 (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
at async Engine.getDefaultVersion (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
at async Engine.executePackageManagerRequest (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23102:5)
Node.js v23.4.0
==> ERROR: A failure occurred in build().
Aborting...
Orche commented on 2025-02-08 23:13 (UTC)
Hey, don't know if it was asked before, but instead of using the node.js package and then enabling pnpm through corepack, wouldn't it be better to just use the pnpm package from the extra repo? it would take less resources and would also mean that pnpm would be up to date with version 10.
bobbyballing commented on 2024-10-18 15:54 (UTC)
hey everyone, i can't seem to be able to compile. i ran yay -S vesktop
and it just doesn't launch. i am cleanbuilding the app.
Progress: resolved 0, reused 553, downloaded 0, added 578, done
Done in 1.6s
> vesktop@1.5.3 build /home/archuser/.cache/yay/vesktop/src/Vesktop-1.5.3
> tsx scripts/build/build.mts
• electron-builder version=25.1.8 os=6.11.3-arch1-1
• loaded configuration file=package.json ("build" field)
• description is missed in the package.json appPackageFile=/home/archuser/.cache/yay/vesktop/src/Vesktop-1.5.3/package.json
• writing effective config file=dist/builder-effective-config.yaml
• executing @electron/rebuild electronVersion=31.1.0 arch=x64 buildFromSource=false appDir=./
• installing native dependencies arch=x64
• completed installing native dependencies
• packaging platform=linux arch=x64 electron=31.1.0 appOutDir=dist/linux-unpacked
⨯ zip: not a valid zip file
github.com/develar/app-builder/pkg/archive/zipx.(*Extractor).extractAndWriteFile
/Users/runner/work/app-builder/app-builder/pkg/archive/zipx/unzip.go:234
github.com/develar/app-builder/pkg/archive/zipx.Unzip.func1.1
/Users/runner/work/app-builder/app-builder/pkg/archive/zipx/unzip.go:104
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
/Users/runner/work/app-builder/app-builder/pkg/util/async.go:68
runtime.goexit
/Users/runner/hostedtoolcache/go/1.21.13/arm64/src/runtime/asm_amd64.s:1650
⨯ /home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/app-builder-bin@5.0.0-alpha.10/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1 failedTask=build stackTrace=Error: /home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/app-builder-bin@5.0.0-alpha.10/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1
at ChildProcess.<anonymous> (/home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/builder-util@25.1.7/node_modules/builder-util/src/util.ts:255:14)
at Object.onceWrapper (node:events:633:26)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
==> ERROR: A failure occurred in build().
Aborting...
-> error making: vesktop-exit status 4
-> Failed to install the following packages. Manual intervention is required:
vesktop - exit status 4
what is the issue at hand here?
Pinned Comments
Edu4rdSHL commented on 2024-09-17 03:25 (UTC) (edited on 2024-10-27 20:33 (UTC) by Edu4rdSHL)
As of 2024-09-16, this package is being co-maintained by official vesktop developers, and any packaging decisions they make will not be questioned on my part unless it's something harmful for the users, which is very unlikely to happen. As I see it coming, they will not use the system's electron on this package purposely, if you don't like it, use
vesktop-electron
, which is also maintained by the same devs.Thanks!