Package Details: vscodium 1.95.3.24321-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.69
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2024-11-16 02:00 (UTC)

Pinned Comments

Latest Comments

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

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

petronny commented on 2022-10-10 09:17 (UTC)

@eclairevoyant Yes. arch4edu always builds in clean chroots.

eclairevoyant commented on 2022-10-07 15:18 (UTC)

looks like it's failing in get_repo.sh. was this tested in a clean chroot?

petronny commented on 2022-10-07 09:55 (UTC)

The current PKGBUILD fails to build.

fatal: not a git repository (or any of the parent directories): .git
==> ERROR: A failure occurred in build().

https://github.com/arch4edu/cactus/actions/runs/3201909310/jobs/5234412365

petronny commented on 2022-09-10 07:52 (UTC)

If you are building in a chroot, make sure package systemd-sysvcompat is installed on your system.

To be more clear, install systemd-sysvcompat in the chroot, which can also be done by adding it to makedepends.

BTW, the arch4edu repository starts to providing the prebuilt binary of vscodium.

cedricroijakkers commented on 2022-09-05 10:41 (UTC)

NOTE: If you are building in a chroot, make sure package systemd-sysvcompat is installed on your system, as this is required for nvm. This cannot be included in the dependencies, since it will break on non-systemd distributions.

buzo commented on 2022-09-05 09:57 (UTC)

Building in a clean chroot fails for me:

==> Extracting sources...
  -> Creating working copy of vscodium git repo...
Cloning into 'vscodium'...
done.
Switched to a new branch 'makepkg'
==> Starting build()...
Downloading and installing node v16.14.2...
Binary download failed, trying source.
==> ERROR: A failure occurred in build().
    Aborting...

MithicSpirit commented on 2022-08-23 18:59 (UTC)

Can confirm that making the package is working fine for me in a clean chroot (other than the nvm bug that requires /sbin/init to exist).

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