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 .. 4 5 6 7 8 9 10 11 Next › Last »

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.

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.)

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