Package Details: vscodium 1.99.32704-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: 77
Popularity: 2.17
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2025-04-22 17:24 (UTC)

Pinned Comments

Latest Comments

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

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

MithicSpirit commented on 2022-10-10 17:29 (UTC)

@eclairevoyant Maybe, although it would be easier to just specify the commit/tag in a fragment.

petronny commented on 2022-10-10 17:26 (UTC) (edited on 2022-10-10 17:27 (UTC) by petronny)

@MithicSpirit You are right. They change the upstream in this commit. https://aur.archlinux.org/cgit/aur.git/commit/?h=vscodium&id=0c03f4bf401d3c50b52cb7e8bd46529be129153c

@eclairevoyant Never mind.

eclairevoyant commented on 2022-10-10 15:58 (UTC) (edited on 2022-10-10 15:59 (UTC) by eclairevoyant)

@petronny Sorry if I wasn't clear, my question was not towards you, it was towards the maintainers if they tested in a clean chroot before uploading this version. I was getting the same error when I tried building.

@MithicSpirit if the issue is with version.sh, imo the maintainers should work with upstream to identify/create a script that works when building from source tarball. I don't think we should patch upstream scripts if possible.

MithicSpirit commented on 2022-10-10 15:11 (UTC)

Getting this same issue on my machine when using a clean chroot. I think that the problem is in version.sh [1] as it attempts to get the current version of the vscodium repo (which doesn't have a .git since we are getting it from github releases). The issue does not occur when not building in a chroot (tested in a clean docker container) since the vscodium folder is inside the folder with the PKGBUILD, which does have a .git since it was git cloned from the AUR (thought the version will likely be incorrect).

[1] https://github.com/VSCodium/vscodium/blob/master/version.sh

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