Package Details: vscodium-git 1.70.1.r0.gf05272f-1

Git Clone URL: (read-only, click to copy)
Package Base: vscodium-git
Description: Free/Libre Open Source Software Binaries of VSCode (git build from latest commit).
Upstream URL:
Licenses: MIT
Provides: codium
Submitter: Salamandar
Maintainer: cedricroijakkers
Last Packager: cedricroijakkers
Votes: 4
Popularity: 0.163189
First Submitted: 2020-03-24 09:33 (UTC)
Last Updated: 2022-08-11 06:41 (UTC)

Pinned Comments

cedricroijakkers commented on 2021-04-10 15:26 (UTC)

This package is now the git build of the very latest commit on the VSCodium branch. If you wish to use the latest released version, switch to the vscodium package.

Latest Comments

willemw commented on 2022-08-19 11:57 (UTC)

Please add vscodium to conflicts and provides. When trying to install VSCodium, vscodium-git is not in the list of options:

:: Resolving dependencies...
:: There are 2 providers available for vscodium:
:: Repository AUR:
    1) vscodium  2) vscodium-bin

Ashark commented on 2022-07-05 23:23 (UTC)

Can you please add vscode to provides array? See

Ashark commented on 2022-06-20 19:42 (UTC)

@cedricroijakkers, thanks for your work. But you really should not update the package every commit. This is extra work and makes noise in history of a package. See

Ashark commented on 2022-05-12 08:22 (UTC)

Thank you.

cedricroijakkers commented on 2022-05-12 06:33 (UTC)

@Ashark: This package tracks the latest commit in the master branch of the vscodium.git repo in GitHub. VSCodium itself determines which commit in the vscode.git (Microsoft) repository they track. So if there is a commit in the vscode.git repo you would like to build, that is solely up to VSCodium. We are just tracking the changes in the vscodium.git repo here. What you would want, is a build of code-git, which is not VSCodium, but VSCode directly. I don't know if that package exists, though.

Ashark commented on 2022-05-11 21:32 (UTC)

Can anybody explain how this package works? I gust rebuilt it, hoping it will include a recent commit to not escape redirection symbol ( But I get a build of vscodium-git, in which's about window I see commit another commit number. The function I look for is not working.

I guess it may drop a very top commits. Is that true?

willemw commented on 2021-10-26 12:47 (UTC)

provides=('vscodium') is missing. 'vscodium-bin' in 'conflicts' is not necessary.

cedricroijakkers commented on 2021-09-07 11:34 (UTC)

@TedHartDavis: I hate M$ just as much as the next guy, but in this case it is actually on the team behind VSCodium. They take the VSCode code, and apply various patches to it, and it is one of these patches that is failing here.

Either way, since 1.60.0 has been released last night, they have fixed the issue, so the build is working again now. Probably they were in the process of merging the upstream code and making it work. I've noticed this happens usually a few days before the final release.

TedHartDavis commented on 2021-09-07 11:27 (UTC)

@cedricroijakkers that just makes me all the more disappointed with M$ (:

It's good to know that it's on them.

Thanks! (:

cedricroijakkers commented on 2021-09-06 06:53 (UTC)

@TedHartDavis that's indeed a problem upstream, it happens quite often that their main branch does not even build. With a bit of luck they should fix it in a couple of days, sadly there is nothing I can do about that...

TedHartDavis commented on 2021-09-05 00:45 (UTC)

Heyo! I presently lack the mental capacity to try to interpret this, but attempting to upgrade in paru, I can't.

Is this more of an upstream issue -- and one that will be fixed before anyone sees this comment? Maybe. Anyway, here's a shortened-for-brevity sequence leading to failure.

==> Starting build()...
applying patch: ../patches/fix-cors.patch
error: patch failed: src/main.js:174
error: src/main.js: patch does not apply
==> ERROR: A failure occurred in build().

MithicSpirit commented on 2021-07-16 02:57 (UTC)

There should be a warning telling people to install jq prior to running makepkg because, even though it is in makedepends, since the PKGBUILD is sourced before installing dependencies (for obvious reasons), and jq is run when sourced (for the $source array), it will fail if jq is not installed. Ideally it would be possible to somehow wait to run jq until prepare() but ¯\_(ツ)_/¯

slimb commented on 2021-06-20 17:45 (UTC)

Since this package is a bit weird, and since someone may just be interested to see the latest vscodium update, but someone else may want to rebuild as soon as the latest vscode update hits, I think the only way to solve this issue for everyone would be to split this into 2 PKGBUILDs. One which tracks the latest vscodium commit, and one which tracks the latest vscode commit. And then you could put back in the pkgver function and not have to manually update this every other day.

MithicSpirit commented on 2021-05-20 12:13 (UTC)

I mean considering this is a -git package, breaking changes are the expectation, though it might be better to just go off of the latest vscodium commit and latest compatible vscode commit, in whichc case the pkgver should just be based on the vscodium commit imo.

cedricroijakkers commented on 2021-05-20 06:12 (UTC) (edited on 2021-05-20 06:13 (UTC) by cedricroijakkers)

What @slimb says actually already happened a few times. I've tried tracking the master branch of vscodium and the main branch of vscode, but that would regularly break since Microsoft would make changes that are not fixed in vscodium yet.

This is why I'm using the same script the vscodium build is using to determine which tag of vscode to check out, but this needs to happen at build time, I cannot simply do this at source=() time, making this build tricky, and pkgver() not update automatically in the AUR.

I think the only thing I can do is set up a CI that tracks the vscodium master branch, executes the build and pushes the update to the AUR git repo.

slimb commented on 2021-05-20 05:56 (UTC)

@MithicSpirit wouldn't it be safer to just wait for vscodium to update incase vscode has breaking change?

MithicSpirit commented on 2021-05-20 02:37 (UTC)

@cedricroijakkers you could try checking other package's pkgver(). The only difference this one should have to most other -git packages is to mark both the vscodium commit and the vscode commit in the version imo.

cedricroijakkers commented on 2021-05-19 07:15 (UTC)

Interesting. I've bumped the version manually now. I need to investigate how the automatic git version updating works in the pkgver() function, since what I have in the code now obviously doesn't work.

Anyway, for now, we're up to the latest version.

MithicSpirit commented on 2021-05-18 20:09 (UTC)

@cedricroijakkers looking at your previous (and pinned) comment I think you might have forgotten to push this change. The current PKGBUILD still pulls from the commit with tag 1.55.1, rather than latest commit.

slimb commented on 2021-04-10 20:55 (UTC)


cedricroijakkers commented on 2021-04-10 15:26 (UTC)

This package is now the git build of the very latest commit on the VSCodium branch. If you wish to use the latest released version, switch to the vscodium package.

slimb commented on 2021-04-08 06:42 (UTC)

Can you move this package to vscodium? -git packages are usually used for packages which target the latest commit automatically. This is just a source build which would be well suited with package name vscodium

cedricroijakkers commented on 2021-03-16 06:58 (UTC)

Thanks for the recommendation CAofRH, I've updated the build.

CAofRH commented on 2021-03-14 01:18 (UTC)

The TRAVIS_OS_NAME env variable isn't really doing anything right now, only the unset OS_NAME is. In fact, a specific part of the build process is being skipped because of the OS_NAME variable not being set to anything. I suggest replacing TRAVIS_OS_NAME for OS_NAME in the PKGBUILD.

brody commented on 2021-01-14 08:00 (UTC)

I assume you use the official docker image "archlinux:base". But if you would use the other official docker image "archlinux:base-devel" then the needed core packages are installed.

cedricroijakkers commented on 2021-01-13 07:57 (UTC)

You are right, but I've left them in, because they are not in the default archlinux docker image, and without them the build wouldn't work. I'm currently working on setting up a build pipeline based on containers to test the build on a permanent basis.

brody commented on 2021-01-13 07:48 (UTC)

The only missing makedepends was python. The other 4 packages: patch, make, gcc and pkg-config (pkgconf) are not needed to include in the makedepends variable because they are in the core repository and therefore installed by default in a clean chroot environment. See wiki

cedricroijakkers commented on 2021-01-12 09:48 (UTC)

Thanks for the build log @dr460nf1r3, very helpful. I've reproduced the issue in a clean Arch install, and added the necessary make dependencies. Build should succeed now, please give it another try with version 1.52.1-2.

dr460nf1r3 commented on 2021-01-12 07:22 (UTC)

This sadly does not build at all in a clean chroot, log attached

slimb commented on 2020-11-15 09:05 (UTC)

Thanks for fixing the package @cedricroijakkers! What was the reason for removing the pkgver function?

cedricroijakkers commented on 2020-09-25 07:50 (UTC)

I have adopted this package, fixed it, and updated it to the latest release again. Please give it a try :-)

alicealice commented on 2020-06-19 22:36 (UTC)

This pkg seems broken to me.

alicealice commented on 2020-06-19 22:00 (UTC)

npm needs to be added as a build dependency.