| Git Clone URL: | https://aur.archlinux.org/vscodium.git (read-only, click to copy) |
|---|---|
| Package Base: | vscodium |
| Description: | Free/Libre Open Source Software Binaries of VSCode (git build from latest release). |
| Upstream URL: | https://github.com/VSCodium/vscodium.git |
| Licenses: | MIT |
| Conflicts: | codium, vscodium, vscodium-bin, vscodium-git |
| Provides: | codium, vscodium |
| Submitter: | cedricroijakkers |
| Maintainer: | cedricroijakkers (daiyam) |
| Last Packager: | daiyam |
| Votes: | 76 |
| Popularity: | 2.39 |
| First Submitted: | 2021-04-10 15:12 (UTC) |
| Last Updated: | 2025-03-08 21:14 (UTC) |
Hi, I tried to install vscodium 1.80.2.23209-1, but got a couple of errors that some URL's can not be redeclared (like serviceUrl, searchUrl, itemUrl, controlUrl) at starting src/vs/platform/product/common/product.ts.
Does anyone know something about this behaviour?
UPDATE: false alarm. I restarted a couple of times (once wasn't enough), and eventually the update worked shrugs
ORIGINAL COMMENT:
I'm trying to install the latest build ("1.75.0.23033-1"), with pamac update -a, but the build fails with the below error:
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild
Output:
/var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild/install.js:93
throw new Error(`Expected ${JSON.stringify("0.15.5")} but got ${JSON.stringify(stdout)}`);
^
Error: Expected "0.15.5" but got "0.17.5"
at validateBinaryVersion (/var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild/install.js:93:11)
at /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild/install.js:240:5
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command
I notice what it mentions about the esbuild version - my version is indeed "0.17.5". But looking at the dependencies for vscodium, I don't see esbuild mentioned anywhere. Does it really depend on version "0.15.5"? Or is there something else happening here that I'm not understanding?
and the checksum doesn't match the github file
I'm getting:
Failure while downloading https://github.com/VSCodium/vscodium/releases/download/1.74.2.23007/VSCodium-linux-x64-1.74.2.23007.tar.gz
with the latest PKGBUILD. There doesn't seem to be a Linux x64 download in the list of assets for this release... or maybe you were too quick and they just haven't built yet?
Update: It's there now. That's just never happened to me before.
Weird, the problem I had does not appear on a different machine...
@eclairevoyant I made a typo, I meant "After installing version 1.74.0.22342-1..." I'll fix the comment. I'm also building my packages in a clean chroot. The command reports this for the broken version:
{
"name": "VSCodium",
"version": "1.74.0",
@lahwaacz the current version is 1.74.0.22342-1, I would try building that in a clean chroot and installing that first.
If you still have issues please post the output for the following command:
head -n3 /usr/share/vscodium/resources/app/package.json
After installing version 1.74.0.22342-1 of this package, VSCodium no longer "sees" any installed extensions, though they are still in ~/.vscode-oss/extensions/ and ~/.vscode-oss/extensions/extensions.json looks correct too. Downgrading to version 1.73.1.22314-1 makes the installed extensions available again. Is there some compatibility problem?
looks like systemd-sysvcompat isn't required anymore? nvm finally had a release after over a year.
It should be fixed in the new release. It's an oversight from me when I've moved to the new build process.
Pinned Comments