Package Details: vscodium 1.96.2.24355-1

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: 73
Popularity: 1.84
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2024-12-21 01:24 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »

murchu27 commented on 2023-02-03 14:34 (UTC) (edited on 2023-02-03 15:05 (UTC) by murchu27)

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?

macxcool commented on 2023-01-07 15:31 (UTC)

and the checksum doesn't match the github file

macxcool commented on 2023-01-07 13:21 (UTC) (edited on 2023-01-07 15:28 (UTC) by macxcool)

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.

lahwaacz commented on 2022-12-13 20:38 (UTC)

Weird, the problem I had does not appear on a different machine...

lahwaacz commented on 2022-12-11 21:42 (UTC)

@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",

eclairevoyant commented on 2022-12-11 21:36 (UTC)

@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

lahwaacz commented on 2022-12-11 20:44 (UTC) (edited on 2022-12-11 21:42 (UTC) by lahwaacz)

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?

eclairevoyant commented on 2022-10-17 16:09 (UTC)

looks like systemd-sysvcompat isn't required anymore? nvm finally had a release after over a year.

daiyam commented on 2022-10-12 07:23 (UTC)

It should be fixed in the new release. It's an oversight from me when I've moved to the new build process.

lahwaacz commented on 2022-10-12 05:55 (UTC)

Since the maintainer does not respond here, I've created an issue on github: https://github.com/VSCodium/vscodium/issues/1290

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »