Package Details: vscodium 1.70.1-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
Provides: codium
Submitter: cedricroijakkers
Maintainer: cedricroijakkers
Last Packager: cedricroijakkers
Votes: 43
Popularity: 3.89
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2022-08-11 06:45 (UTC)

Pinned Comments

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

This package was previously called vscodium-git. This is the latest release, building from git. The package vscodium-git is the very latest commit on the VSCodium branch.

Latest Comments

MithicSpirit commented on 2022-08-11 20:41 (UTC) (edited on 2022-08-11 21:13 (UTC) by MithicSpirit)

@eclairevoyant nvm depends on systemd-syscompat (or in general the existence of a /sbin/init). You'll have to add that to the make dependencies if you want to build in a chroot.

EDIT: note that this is not currently a make dependency in this pkgbuild or a regular dependency in nvm because of non-systemd users. AFAIK this has been fixed upstream, but the fix has not yet been released.

eclairevoyant commented on 2022-08-11 06:20 (UTC)

Has anyone successfully built this in a chroot? When I try, I get this error:

$ makechrootpkg -r $CHROOT -I /var/lib/repo/aur/nvm-0.39.1-1-any.pkg.tar.zst
[snip...]
==> Starting build()...
Downloading and installing node v16.14.2...
Binary download failed, trying source.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check [/path/to/chroot/user/build]

It's clearly failing at the nvm install command, but I'm not sure why this happens because building outside of a chroot works fine. I can also run nvm install v16.14.2 in some random dir and that works fine as well.

P0rc0R0550 commented on 2022-07-23 12:04 (UTC) (edited on 2022-08-09 18:50 (UTC) by P0rc0R0550)

I use the fix proposed here, here the code I used. Now it complete the process, but takes always long time, how you can see here

PS: I think my notebook isn't real bad, how you can see here, and I think if the script can be rewrite to run in parallels, so we can do it more efficiently

PS2: Today I update the package, but the issue still exist (it takes 47minutes and 26 second to complete):

while ps -o pid,comm,cmd,start,etime -p "98520"; do sleep 1; done
|   PID   | COMMAND |             CMD             |  STARTED  | ELAPSED |
|  98520  |   sed   | sed -i -E s/[^/]+\.data\.mi |  19:41:35 |  47:26  |

cedricroijakkers commented on 2022-07-21 06:24 (UTC)

I had noticed the slow build too since the last version. This is something upstream, which I have reported in the following bug: https://github.com/VSCodium/vscodium/issues/1165

MithicSpirit commented on 2022-07-21 03:22 (UTC)

undo_telemtry.sh works fine, it just takes a while to run since it needs to grep through all of the files and then sed through all of the matching ones (see the source). Didn't time mine but I know it took a long; if you want to make sure it is still working you can check a system resource monitoring tool like htop, as grep or sed should be hovering around 100% CPU usage.

That said, it is probably possible to have it run multiple sed processes simultaneously (one for each file), which would probably speed this process up greatly, though this would require rewriting the script. It would also be important to parse $MAKEFLAGS to limit the number of simultaneous processes.

jotoho commented on 2022-07-20 22:25 (UTC)

I can confirm that attempting to update aur/vscodium from version 1.69.1-1 to 1.69.2-1 with the yay AUR helper causes the script to get stuck with the last line being "++ ../undo_telemetry.sh"

I was forced to cancel the build attempt.

P0rc0R0550 commented on 2022-07-20 21:47 (UTC)

Remain hours with last display ../undo_telemetry.sh, without return a code error. Follow paste. Please fix it.

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

Can you please add vscode to provides array? See https://wiki.archlinux.org/title/Talk:Visual_Studio_Code#Provides_array_for_flavor_packages

cedricroijakkers commented on 2022-06-14 10:07 (UTC)

@willgame: Looks like you cannot DNS lookup the URL registry.yarnpkg.com. This is where packages are downloaded which are needed for the build. Not much we can do about this, except wait for the URL to come back up.

willgame commented on 2022-06-14 09:19 (UTC) (edited on 2022-06-14 09:20 (UTC) by willgame)

I got an error. What is wrong?

https://sebsauvage.net/paste/?15b75dc540228f7a#/Km5tRt4UH2i8XedipJ17CHi9nEKD7DRyeIajWppKro=

6543 commented on 2022-05-17 13:22 (UTC) (edited on 2022-05-17 13:24 (UTC) by 6543)

@cedricroijakkers never mind created systemd-sysvcompat-noop that does exactly nothing :)

-> https://aur.archlinux.org/packages/systemd-sysvcompat-noop

cedricroijakkers commented on 2022-05-17 13:21 (UTC)

@KerfuffleV2 @6543: Well, this is going to be a problem. I cannot add the openrc package, because this will break for people using systemd. And the other way around. And then there are people using runit or some other init. For now, I can only remove the make dependency, since there is no optional version of that. When building in a chroot, you'll have to either install the package manually or add the init executable in some way.

6543 commented on 2022-05-17 13:03 (UTC) (edited on 2022-05-17 13:05 (UTC) by 6543)

Hi @KerfuffleV2, @cedricroijakkers - I kan understand why you did add systemd-sysvcompat but this breaks my openrc system if I would let it run!!!

can you add openrc as alternative to systemd-sysvcompat ?

KerfuffleV2 commented on 2022-05-10 13:18 (UTC) (edited on 2022-05-10 13:19 (UTC) by KerfuffleV2)

@cedricroijakkers: Were you building it in a chroot though? I also use paru with Chroot in /etc/paru.conf.

When building in a chroot, extra packages in your local installation aren't available. if the build requires anything that's not in the default package set then it has to be specified in makedepends to ensure it is pulled in.

Thanks for adding that!

cedricroijakkers commented on 2022-05-09 06:22 (UTC)

@KerfuffleV2: I did not have any problems building myself in paru, but I did have the package installed already. I've added it to the dependency list now.

KerfuffleV2 commented on 2022-05-08 08:40 (UTC) (edited on 2022-05-08 08:41 (UTC) by KerfuffleV2)

It doesn't seem possible to build this package in a chroot right now. nvm fails with a very unhelpful error message because deep in its guts it does:

L=$(ls -dl /sbin/init 2>/dev/null)

As /sbin/init does not actually exist, the command returns a non-zero status and nvm just gives up immediately due to running with set -e. It looks like the latest nvm in the repo has a fix for this problem, but unfortunately that's not the version that's used to build vscodium.

The simplest solution right now is to add systemd-sysvcompat to the makedepends section of the PKGBUILD. This will ensure /sbin/init actually exists, even when building chrooted.

reclusivesage commented on 2021-11-19 17:23 (UTC) (edited on 2022-03-11 17:29 (UTC) by reclusivesage)

Edit (March 11, 2022): I was able to install vscodium again without issue a few days ago. Maybe my Pacman updates were very out of date.

When I tried updating, I got this error. What can I do?

==> Validating source files with sha256sums...
    vscodium ... Skipped
    vscode ... Skipped
    vscodium.desktop ... Passed
==> Extracting sources...
  -> Creating working copy of vscodium git repo...
Cloning into 'vscodium'...
done.
Switched to a new branch 'makepkg'
  -> Creating working copy of vscode git repo...
Cloning into 'vscode'...
done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting build()...
==> ERROR: A failure occurred in build().
    Aborting...

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

The conflicts array is not necessary. See example in https://wiki.archlinux.org/title/PKGBUILD#conflicts.

Already installed and don't need to be listed: bash gcc gcc-libs make.

Spartan322 commented on 2021-09-22 14:37 (UTC)

I commented out that section in my global config @jotoho and it made it to compilation, so both [lfs] and [filter "lfs"] seem to contain the issue at least.

jotoho commented on 2021-09-17 04:21 (UTC)

My global git config file had no [lfs] section when the update failed. (At path ~/.config/git/config, not ~/.gitconfig) Switched to vscodium-bin in the meantime to avoid this issue.

The only thing related to lfs in it is this snippet:

[filter "lfs"]
        clean = git-lfs clean -- %f
        smudge = git-lfs smudge -- %f
        process = git-lfs filter-process
        required = true

reclusivesage commented on 2021-09-17 04:13 (UTC) (edited on 2021-09-17 04:14 (UTC) by reclusivesage)

Much thanks to @HurricanePootis, I'm confirming your suggestion works for me.

Before seeing your comment, I still had same the Git LFS issue I had before, despite having git-lfs installed. You may be having the same issue if you don't actively use Git LFS anymore. (For me, I was playing with Git LFS on Keybase a few weeks ago, until I realized I actually only needed normal Git. The LFS section in ~/.gitconfig must've been left over from then.)

(I'm not sure what the suggestion of @HurricanePootis means for those who need &/or actively use Git LFS.)

HurricanePootis commented on 2021-09-17 02:12 (UTC)

To anyone having problems with git cloning the repo, even after installing git-lfs, I have found a fixed that work and may work for y'all too.

Remove anything under the [lfs] section in your ~/.gitconfig file.

cedricroijakkers commented on 2021-09-16 09:30 (UTC)

Interesting. I never had git-lfs installed on my system, yet never had any compilation issues. I've added it to the make dependencies now, so try again if that solves your issue. Otherwise, the only thing I can recommend is to clean the build cache of your AUR helper (paru in my case). With a clean cache I can build the software correctly at this point.

frankenstein20 commented on 2021-09-16 06:26 (UTC)

hi @HurricanePootis I have git-lfs on my system, but as you can see... it fails as well

HurricanePootis commented on 2021-09-15 21:29 (UTC)

Heads up, vscodium apparently requires the package git-lfs as a makedepends, seeing as it has large files it needs to git clone

==> Extracting sources...
  -> Creating working copy of vscodium git repo...
Cloning into 'vscodium'...
done.
git-lfs filter-process: line 1: git-lfs: command not found
fatal: the remote end hung up unexpectedly
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

jotoho commented on 2021-09-15 19:38 (UTC)

I have the same issue updating this AUR package as @frankenstein20 and @reclusivesage.

reclusivesage commented on 2021-09-15 16:12 (UTC) (edited on 2021-09-15 16:16 (UTC) by reclusivesage)

Edit: Just realized user frankenstein20 had the same issue.

Is there anything I can do about the Git LFS error below?

When I tried updating VSCodium today, I got this:

==> Extracting sources...
  -> Creating working copy of vscodium git repo...
Cloning into 'vscodium'...
done.
Downloading build/windows/rtf/TXT2RTF.zip (374 KB)
Error downloading object: build/windows/rtf/TXT2RTF.zip (c3eac99): Smudge error: Error downloading build/windows/rtf/TXT2RTF.zip (c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9): error transferring "c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9": [0] remote missing object c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9

Errors logged to /home/uSER/AUR/vscodium/src/vscodium/.git/lfs/logs/20210915T120535.641902055.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: build/windows/rtf/TXT2RTF.zip: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

==> ERROR: Failure while creating working copy of vscodium git repo
    Aborting...

Here are the contents of /home/uSER/AUR/vscodium/src/vscodium/.git/lfs/logs/20210915T120535.641902055.log: https://bin.snopyta.org/?52228647825f1dfe#DezmRxLnP67WvBJQZpGWxNzi76SAjDRJYzvzBM8G6d4N

frankenstein20 commented on 2021-09-11 14:44 (UTC)

somehow I get an error :(

Error downloading object: build/windows/rtf/TXT2RTF.zip (c3eac99): Smudge error: Error downloading build/windows/rtf/TXT2RTF.zip (c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9): error transferring "c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9": [0] remote missing object c3eac997fba9d3d5596c503a826fe5d54c87b1cf899a790b6d077e4d196bd5e9

Direct-A commented on 2021-08-24 17:36 (UTC)

For someone have problem to use extension: Visual Studio IntelliCode.

If you get a ERROR: Sorry, something went wrong activating IntelliCode support for Python. Please check the "Python" and "VS IntelliCode" output windows for details.

And in OUTPUT -> VS IntelliCode: Language server is set to Pylance. Acquiring model Acquiring model 'intellisense-members-lstm-pylance' for python Querying IntelliCode service for available models. vs-intellicode-python was passed a model: {}. Cached model is up to date. Activating Python extension Language server extension command failed. Exception: Error: command 'python.intellicode.loadLanguageServerExtension' not found at g._tryExecuteCommand (file:///usr/share/vscodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1523:3364) at file:///usr/share/vscodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1523:3245 at processTicksAndRejections (internal/process/task_queues.js:93:5) Error while activating Python: {}

!!!!!!!! Install vscodium-features will solve this problem !!!!!!!!

patlefort commented on 2021-07-26 00:12 (UTC)

This package does conflict with code as it install a file /usr/bin/code.

cedricroijakkers commented on 2021-06-14 11:14 (UTC)

@kearneyBack: There is indeed no reason why vscodium should not play together with code. I've updated the provides and conflicts configs to be less strict. You can install both next to each other now.

kearneyBack commented on 2021-06-14 11:05 (UTC)

why install this need to remove the package code ? can they play together?

BrLi commented on 2021-05-13 05:37 (UTC)

@cedricroijakkers yw.

https://github.com/Brli/vscodium/blob/master/PKGBUILD

cedricroijakkers commented on 2021-05-12 08:06 (UTC)

@BrLi: As far as I know, this is the same build method as the vscodium repo uses. Keep in mind that this is not the same as vscode itself, but a stripped-from-all-telemetry open source version. If you want normal vscode, you need to install the code package. If you have any ideas on optimising the build process of Codium, please do tell.

BrLi commented on 2021-05-11 21:20 (UTC)

Hi, is it possible that you switch to use the build method of vscode from official repo, that doesn't include the full binary of electron/chromium stack?

as the size would be much smaller.

tyler19820201 commented on 2021-04-19 09:03 (UTC)

@cedricroijakkers: Ok. I will try again but this time will remove vscodium-git before start building this package... Thanks for quick respond anyway.

cedricroijakkers commented on 2021-04-19 08:56 (UTC)

@tyler19820201: I always use paru myself as an AUR helper, that seems to be a little quicker. But I've just tried it in pamac, and I've managed to build VSCodium just fine. It did take quite some time to git clone the Microsoft repository, but it finished in the end and worked fine. I can only recommend to just try it again. Occasionally I get some failure in building at a random step, but just running the build again then solves the issue. It should keep the downloaded files, so there is no need to re-clone everything.

Technically speaking, both vscodium and vscodium-git do the exact same build, just from another branch in git.

tyler19820201 commented on 2021-04-19 08:37 (UTC)

I was trying to install it from pamac but after 30 minutes trying the installation has been aborted & failed for some error. But vscodium-git 1.55.0.r0.gd8a91cf-1 has been succesfully installed in around 25 minutes...

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

This package was previously called vscodium-git. This is the latest release, building from git. The package vscodium-git is the very latest commit on the VSCodium branch.