and the checksum doesn't match the github file
Search Criteria
Package Details: vscodium 1.95.3.24321-1
Package Actions
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.69 |
First Submitted: | 2021-04-10 15:12 (UTC) |
Last Updated: | 2024-11-16 02:00 (UTC) |
Dependencies (23)
- alsa-lib
- cairo (cairo-gitAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libnotify (libnotify-gitAUR)
- libxkbfile
- libxss
- libxtst
- nss (nss-hgAUR)
- git (git-gitAUR, git-glAUR) (make)
- git-lfs (git-lfs-gitAUR) (make)
- gulp (gulp-cliAUR) (make)
- jq (jq-gitAUR) (make)
- libxdmcp (make)
- nvmAUR (nvm-gitAUR) (make)
- patch (patch-gitAUR) (make)
- pkg-config (pkgconf-gitAUR, pkg-config-gitAUR, pkgconf) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-distutils-extra (make)
- Show 3 more dependencies...
Required by (2)
Sources (4)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »
macxcool commented on 2023-01-07 15:31 (UTC)
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
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.
Pinned Comments