Package Details: vscodium-electron

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

Latest Comments

1 2 3 4 5 Next › Last »

MithicSpirit commented on 2024-04-12 23:39 (UTC) (edited on 2024-04-12 23:40 (UTC) by MithicSpirit)

@fredricocalamari yeah it looks like the branch issue has been fixed. I wasn't having issues with this build, though (other than noticing the strange git situation).

@ironveil can you confirm it has been fixed for you as well? You might have to delete this package from yay's PKGBUILD cache (if it even has one? I don't use yay), since the cloned repo might be in a weird state.

fredricocalamari commented on 2024-04-12 23:04 (UTC)

@MithicSpirit I just successfully rebuilt the latest submit this time using yay to automate the entire process. I selected cleanbuild and it now works as intended, at least on my computer.

MithicSpirit commented on 2024-04-12 22:36 (UTC)

@fredricocalamari I think that the only current issue is that the remote has a detached HEAD. The latest PKGBUILD seems to be working fine.

@Richardn huh that's weird. Good luck, both with git and with your studies.

fredricocalamari commented on 2024-04-12 22:08 (UTC) (edited on 2024-04-12 22:11 (UTC) by fredricocalamari)

I guess I am lucky that I was able to get the package to build on 4/9 right after @Richardn merged the xwayland fix to the repo. If you can roll back to that date and work from there I think you will have more luck fixing the issues others are having considering it worked for me. I had to clone the source and run makepkg. I didn't use yay. I have the fully functioning no-xwayland patched vscodium-electron installed already so I know there is a working configuration. We just need to track it down.

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 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
@@ -91,13 +91,13 @@ prepare() {
    # Remove old build
    if [ -d vscode ]; then
        rm -rf vscode VSCode*

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

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