Package Details: vscodium-electron 1.96.2.24355-1

Git Clone URL: https://aur.archlinux.org/vscodium-electron.git (read-only, click to copy)
Package Base: vscodium-electron
Description: VS Code without MS branding/telemetry/licensing. - System-wide Electron edition
Upstream URL: https://github.com/VSCodium/vscodium
Keywords: code codium electron system vscode vscodium wayland
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: m00nw4tch3r
Maintainer: Richardn
Last Packager: Richardn
Votes: 8
Popularity: 0.31
First Submitted: 2022-04-10 18:19 (UTC)
Last Updated: 2024-12-21 04:31 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Richardn commented on 2024-04-12 21:42 (UTC) (edited on 2024-04-12 21:44 (UTC) by Richardn)

Actually when I first adopted the package I manually tested everything in a manually set up chroot and there was no problems. Probably because I was just being lucky at that time, files scattering in the working dir in a specific pattern that did not yield problems.

About "repository in this weird state": Now I am concerned. Yes, AUR git server was behaving strange yesterday when I made the update. When I git push as usual, the command line signals success all the way to "Writing objects...done", but then everything just hang on my side. I saw that on the webpage the "last updated" number indeed updated, while git was still hanging. I interrupted and tried several times, all the same. After I came back an hour later I saw that the changes are in place in "View Changes" so I be like "well...this means everything works in the end"?

I will look into this when I have the time (poor Computer Engineering student solving and plotting MOSFETs here).

Update: Oh I just tried git push origin master and my git did not hang this time. And cloning is successful.

MithicSpirit commented on 2024-04-12 21:31 (UTC)

@Richardn my "AUR helper" that is causing this is makechrootpkg, which is for building packages in a clean chroot (see the wiki). I've found this helpful for detecting issues in my (and sometimes other's) PKGBUILDs.

@ironveil this issue is because the current remote HEAD is a detached commit. Not sure what exactly happened to put the repository in this weird state, nor how to fix it. Maybe the maintainer can try pushing their master branch manually (git push origin master?).

ironveil commented on 2024-04-12 08:31 (UTC)

The latest version doesn't build from yay, gives me this error:

:: (1/1) Downloaded PKGBUILD: vscodium-electron
 -> error merging /home/ironveil/.cache/yay/vscodium-electron: fatal: No current branch.

Richardn commented on 2024-04-11 22:59 (UTC)

Fixed along with update to 1.88.1.24102. Your AUR helper has its own ideas on where to put $srcdir or where to execute build commands, but yeah, I should not have used ../../.

MithicSpirit commented on 2024-04-09 20:22 (UTC)

Doesn't build for me currently. This patch fixes it:

diff --git a/PKGBUILD b/PKGBUILD
index 6cc87a7..6bdaba5 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -91,13 +91,13 @@ prepare() {
    # Remove old build
    if [ -d vscode ]; then
        rm -rf vscode VSCode*
    fi

    # Mangle original vscodium build script to build against system electron
-   patch -u build.sh -i ../../vscodium-electron.patch
+   patch -u build.sh -i "$srcdir/vscodium-electron.patch"
 }

 build() {
    _ensure_local_nvm
    nvm install "${_nodejs}"
    nvm use "${_nodejs}"

fredricocalamari commented on 2024-04-09 19:10 (UTC) (edited on 2024-04-11 04:13 (UTC) by fredricocalamari)

I can confirm that the Wayland patch by backbord works and xwayland is no longer starting when launching vscodium. The PKGBUILD built successfully. Congratulations to all involved in finally tracking this issue down. This is the holy grail for us wayland users. Since this version is essentially the only correct way of launching vscode in Wayland, and since Wayland is the default on so many distros now, everyone who uses Wayland should switch to using this vscodium-electron build and stop using the vanilla vscodium variant as it offers nothing extra.

Richardn commented on 2024-04-09 14:47 (UTC) (edited on 2024-04-09 14:48 (UTC) by Richardn)

Replying to the latest two comments:

Yeah I can set the provides.

Sorry for the validity check failing, that was me being dumb. I applied the changes backbord proposes to fix problems for Wayland users to vscodium.sh, without updating the sum. Updating soon.

infopcgood commented on 2024-04-09 06:22 (UTC)

vscodium.sh fails sha256sum validity check while installing.

shaybox commented on 2024-04-09 03:00 (UTC)

Could you provide vscodium so this package can be used as replacement for dependencies?

« First ‹ Previous 1 2 3 4 5 6 Next › Last »