That's a weird issue. I think GitHub for some reason reported the wrong version, causing my bot to revert the version. It's however fixed now.
Search Criteria
Package Details: vscodium-bin 1.101.03933-1
Package Actions
| 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: | 337 |
| Popularity: | 8.54 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2025-06-12 22:01 (UTC) |
Dependencies (14)
- alsa-lib
- bash (bash-devel-gitAUR, bash-gitAUR)
- cairo (cairo-gitAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libnotify (libnotify-gitAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- python (python37AUR)
- gvfs (gvfs-gitAUR) (optional) – For move to trash functionality
- libdbusmenu-glib (optional) – For KDE global menu
Required by (7)
- caelestia-meta (requires vscode) (optional)
- vscode-xdg-patch-hook (requires vscode) (optional)
- vscodium-bin-features
- vscodium-bin-marketplace
- vscodium-features (requires vscodium)
- vscodium-marketplace (requires vscodium)
- vscodium-prod-patcher (requires vscodium)
Sources (7)
- https://github.com/VSCodium/vscodium/releases/download/1.101.03933/VSCodium-linux-arm64-1.101.03933.tar.gz
- https://github.com/VSCodium/vscodium/releases/download/1.101.03933/VSCodium-linux-x64-1.101.03933.tar.gz
- vscodium-bin-url-handler.desktop
- vscodium-bin-wayland.desktop
- vscodium-bin.desktop
- vscodium-bin.install
- vscodium-bin.sh
Icelk commented on 2022-02-01 10:27 (UTC)
ajgringo619 commented on 2022-01-31 22:51 (UTC) (edited on 2022-01-31 22:52 (UTC) by ajgringo619)
Based on my pacman history, it looks like v1.63.2-2 was installed, then removed (by me), then reinstalled later:
[2022-01-01] [ALPM] installed vscodium-bin (1.63.2-2)
[2022-01-19] [ALPM] removed vscodium-bin (1.63.2-2)
[2022-01-21] [ALPM] installed vscodium-bin (1.63.2-2)
yay -Ss vscodium-bin shows aur/vscodium-bin 1.63.2-1 (+122 8.97) (Installed: 1.63.2-2)
Icelk commented on 2022-01-31 20:51 (UTC)
@GIgas002 I don’t see any 1.63.2-2 version?
Gigas002 commented on 2022-01-31 20:32 (UTC)
What was the problem with 1.63.2-2 version? It's now displayed, as "newer, than in AUR (1.63.2-1)"? I don't see the sense in two latest commits.
ZorinArch commented on 2021-12-22 13:53 (UTC)
@Icelk Thanks,
Icelk commented on 2021-12-22 13:29 (UTC)
@ZorinArch Done!
ZorinArch commented on 2021-12-22 13:25 (UTC)
Hi @Icelk,
please update checksum of vscodium-bin-marketplace from md5 to sha256.
KDN_Observer commented on 2021-12-21 21:27 (UTC)
@Icelk I tested on both my main machine and a clean Arch VM and everything works as expected. I don't use those downstream packages (such as vscodium-bin-features or vscodium-bin-marketplace) but I guess they need to be patched as well.
Icelk commented on 2021-12-21 17:59 (UTC)
@macxcool Is it working now?
macxcool commented on 2021-12-21 16:31 (UTC)
(1/3) Arming ConditionNeedsUpdate... (2/3) Updating the desktop file MIME type cache... (3/3) [vscodium-bin-marketplace] Patching product.json... sed: can't read /usr/share/vscodium-bin/resources/app/product.json: No such file or directory error: command failed to execute correctly
Pinned Comments
sperg512 commented on 2021-05-12 00:31 (UTC) (edited on 2024-06-04 15:14 (UTC) by sperg512)
@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.