Package Details: vscodium-bin 1.116.02821-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: Icelk
Last Packager: Icelk
Votes: 377
Popularity: 7.85
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2026-04-27 15:00 (UTC)

Pinned Comments

<deleted-account> commented on 2021-05-12 00:31 (UTC)

@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 .. 30 Next › Last »

Icelk commented on 2026-03-24 06:39 (UTC)

@webdawg See https://github.com/Icelk/aur-updater :)

webdawg commented on 2026-03-23 22:14 (UTC)

@icelk, can you release your build and release pipleline here so I can use it for other packages?

Icelk commented on 2026-03-22 18:13 (UTC)

@nervocalm

That's great to hear:)

nervocalm commented on 2026-03-09 21:47 (UTC) (edited on 2026-03-09 22:24 (UTC) by nervocalm)

Hi @icelk, thanks for your reply.

I'm sorry; it was something yay cache-related. It confused me that I received this error even after choosing a clean build. I decided to clean the cache entries manually, and now it works like a charm.

Thank you for your work!

Icelk commented on 2026-03-06 23:42 (UTC)

@nervocalm

Hi! I think you maybe need to update your rust. If youve installed it with rustup, run rustup update

nervocalm commented on 2026-03-06 20:02 (UTC) (edited on 2026-03-06 20:06 (UTC) by nervocalm)

Hi guys!

I am getting a rust error in the last build.

info: component 'rust-std' for target 'x86_64-unknown-linux-gnu' is up to date
+++ cargo build --release --target x86_64-unknown-linux-gnu --bin=code
error: rustc 1.86.0 is not supported by the following packages:
  time@0.3.47 requires rustc 1.88.0
  time-core@0.1.8 requires rustc 1.88.0
Either upgrade rustc or select compatible dependency versions with
`cargo update <name>@<current-ver> --precise <compatible-ver>`
where `<compatible-ver>` is the latest version supporting rustc 1.86.0

++++ error_function build
++++ ((  ! BASH_SUBSHELL  ))
+++++ gettext 'A failure occurred in %s().'
++++ error 'A failure occurred in %s().' build
++++ local 'mesg=A failure occurred in %s().'
++++ shift
+++++ gettext ERROR:
++++ printf $'\E[1m\E[31m==> ERROR:\E(B\E[m\E[1m A failure occurred in %s().\E(B\E[m\\n' build
==> ERROR: A failure occurred in build().

Initially it download the rust 1.86 package

info: using existing install for 'stable-x86_64-unknown-linux-gnu'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.86.0 (05f9846f8 2025-03-31)

RELEASE_VERSION="1.110.01571"
MS_TAG="1.110.0"
MS_COMMIT="0870c2a0c7c0564e7631bfed2675573a94ba4455"

But then time and time-core packages require rust 1.88 at least. Anybody else?

Thanks!

jongeduard commented on 2026-02-13 19:55 (UTC)

@Gianfilippo980 I have !debug set in my own /etc/makepkg.conf anyway, because in my experience those debug packages tend to be problematic anyway (indeed weird conflicts) and their size can also be enormous, wasting a lot of disk space.

They are useful if you actually plan to debug things, but most of the time that's not the case.

Icelk commented on 2026-02-10 09:42 (UTC)

@Gianfilippo980 I removed the debug package. @drakkar1969 It's removed. @jronald these are also fixed by removing the debug symbols

Gianfilippo980 commented on 2026-01-30 10:17 (UTC) (edited on 2026-01-30 10:18 (UTC) by Gianfilippo980)

There seems to be a compatibility problem between "vscodium-bin-debug" and "teams-for-linux-debug" where they try to own the same files. producing a Pacman error: https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error The files in question are in the following directories:

- /usr/lib/debug/.build-id/84/
- /usr/lib/debug/.build-id/8f/
- /usr/lib/debug/.build-id/be/
- /usr/lib/debug/.build-id/cd/
- /usr/lib/debug/.build-id/d3/
- /usr/lib/debug/.build-id/d6/
- /usr/lib/debug/.build-id/f5/
- /usr/lib/debug/.build-id/f6/

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