Package Details: vscodium-bin 1.88.1.24104-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: sperg512 (Icelk)
Last Packager: Icelk
Votes: 271
Popularity: 7.85
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-04-13 02:01 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC)

hey guys, @Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD

Latest Comments

1 2 3 4 5 6 .. 22 Next › Last »

renyuneyun commented on 2024-04-21 13:37 (UTC)

For some reason, when working with Python project, VSCodium says isort failed to start, which in turn complains missing pygls module. Manually installing python-pygls fixes this. But I'm not sure if this is a potential problem for the package itself (e.g. a missing opt-dependency) or due to my configuration. Thought worth mentioning in case others encounter as well.

Icelk commented on 2024-04-14 15:24 (UTC)

@Ranguna Excellent, thanks for investigating!

Ranguna commented on 2024-04-13 20:31 (UTC) (edited on 2024-04-13 20:31 (UTC) by Ranguna)

Indeed, it seems to be the same issue.

I wasn't quite sure why this issue was happening when I first got it, but I've since found out why: https://archlinux.org/news/debug-packages-and-debuginfod/

Seems debug packages are now enabled by default on arch. Here's how they can be disabled: https://bbs.archlinux.org/viewtopic.php?id=292827

That fixed non aur packages for me, but aur ones still generate *-debug installs on my machine. But I think it's because I didn't follow the steps properly and didn't try a second time.

Try giving that a try @qwrtln, hopefully it'll solve the issue on your side.

Icelk commented on 2024-04-13 19:41 (UTC)

@qwrtln Looks like just the error @Ranguna got. Maybe try reinstalling both packages? Because /usr/lib/debug isn't a file we explicitly write to. That seems to be some debugedit shenanigans.

qwrtln commented on 2024-04-09 21:48 (UTC) (edited on 2024-04-09 21:49 (UTC) by qwrtln)

Hello, while trying to install/upgrade this package to vscodium-bin-1.88.0.24096-1, I get the following error:

error: failed to commit transaction (conflicting files)
vscodium-bin-debug: /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1 exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596 exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762 exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95 exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0 exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0.debug exists in filesystem (owned by mullvad-vpn-beta-bin-debug)
Errors occurred, no packages were upgraded.

Indeed I use mullvad-vpn-beta-bin AUR package. According to the article in Archwiki I should file a bug report. What can we do with this?

BryanLiang commented on 2024-03-24 10:41 (UTC)

@Icelk I don't know. It is weird. I tried to build the package via makepkg directly without any AUR helper, but the broken symbolic links still exist.

Icelk commented on 2024-03-23 15:33 (UTC)

@BryanLiang

Yes I am aware, but where do they come from? I don't see their creation in PKGBUILD. This doesn't seem acute since they are benign(?).

BryanLiang commented on 2024-03-21 16:21 (UTC)

@Icelk I go to check the /opt/vscodium-bin after seeing @ZorinArch's comment.

The directory indeed contains multiple broken symbolic links.

Here is the screenshot: https://s2.loli.net/2024/03/22/83WxazUoctL64JD.png

Icelk commented on 2024-03-21 15:55 (UTC)

@ZorinArch

The PKGBUILD doesn't contain commands to link them; at least I'm not seeing it. Please point me in the right direction.

ZorinArch commented on 2024-03-07 09:10 (UTC)

@Icelk, the symlinks inside /opt/vscodium-bin/ do nothing to the app.

1 2 3 4 5 6 .. 22 Next › Last »