| 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: | 311 |
| Popularity: | 7.66 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2024-11-16 02:00 (UTC) |
Hi @fractalf. Thanks!
I've actually answered this question before:
I believe this is done to add codium to the open-with context menu. If you want another app to open, you can always create your own .desktop file (and e.g. open the folder in you terminal of choice) or just remove the default open with choice using the xdg utilities (xdg-mime default nemo.desktop inode/directory).
Hi! There is a bug in this package that messes with 2 things on my EndeavourOS (Cinnamon)
I tracked it down to this line in vscodium-bin.desktop
MimeType=text/plain;inode/directory;
This messes up the file /usr/share/applications/mimeinfo.cache after installing:
# Before install
> cat /usr/share/applications/mimeinfo.cache | grep inode
inode/directory=nemo.desktop;
# After install
> cat /usr/share/applications/mimeinfo.cache | grep inode
inode/directory=codium.desktop;nemo.desktop;
I'm not sure why this (inode/directory) was even added in the first place,
but I'm sure this messes up at least these two things mentioned.
Cheers! :)
Edit: Yea and the fix is to remove inode/directory; from vscodium-bin.desktop, I tried this locally, build it and installed it and all was fine
[managed to install it now, so maybe github just gave me garbage a few times, though I did try it on different connections as well]
@Icelk It's still saying it's the wrong hash (actually looks like the has of the x86_64 file is back to the one you originally put in 1.74.2.23007-1).
Is there a way to refresh any cached sums I might have? I'm still getting a validity check error for the main .tar.gz file
Hey. The issues with the sums should be resolved now. Thanks for notifying me!
The binaries were uploaded to GitHub a few minutes ago, but the hashes for the binaries still need to be updated.
curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://github.com/VSCodium/vscodium/releases/download/1.74.2.23007/VSCodium-linux-x64-1.74.2.23007.tar.gz
@soorajsp
I had some time to look into this today. I can log into a GitHub account, but the settings sync request returns an 401 (see the vscode output for Settings Sync). I've also searched the vscodium git for issues relating to this. I advice you to open an issue over there. The product.json seems to point to the correct endpoint. I suspect VSCodium for some reason doesn't send an authorization header when trying to sync with a GitHub account.
Sorry for the delay.
As for why visual-studio-code-bin works, I think that has to do with Microsoft's proprietary build steps - VSCodium must've missed something.
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.