after update I got a bug:
$ vscodium
/usr/bin/vscodium: line 53: 38749 Segmentation fault ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" --ms-enable-electron-run-as-node "$@"
Did anyone get the same issue?
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: | 327 |
Popularity: | 8.61 |
First Submitted: | 2020-09-23 18:58 (UTC) |
Last Updated: | 2025-04-09 18:00 (UTC) |
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 25 Next › Last »
after update I got a bug:
$ vscodium
/usr/bin/vscodium: line 53: 38749 Segmentation fault ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" --ms-enable-electron-run-as-node "$@"
Did anyone get the same issue?
The 1.62.2 sha256 sum for the ARM64 architecture is wrong in PKGBUILD, here's the correct one: 3a7b9931ab1bc3432ba6e4323c7f0caf280e236d95fc6b30c6cb24e9af925f02 .
Hi @3y3p4tch! I believe it is to allow all features like reading workspaces and other content in the .vscode directory.
Check the vscode docs (or something), since it's just an argument to vscode.
Hi maintainers, I noticed that vscodium-bin.desktop contains 'no-sandbox'. Any particular reason for it being there? If not, then could it be removed? (My build works perfectly without no-sandbox)
@willemw @sperg512 This is now implemented and will be added in the next release by the auto-updater, so we don't push an unneeded change to all using this package.
@willemw yeah, that's what he means, we can just add "vscodium" to provides and it'll pop up that same menu when you yay -S vscodium
.
@Icelk: I would just add 'vscodium' to 'provides' now to this package (and all the other packages you maintain). It is optional to do so and there is no downside.
By "Do all the options appear with a default?" do you mean similar to this:
$ paru -S paru
:: Resolving dependencies...
:: There are 3 providers available for paru:
:: Repository AUR:
1) paru 2) paru-bin 3) paru-git
Enter a number (default=1):
Answer is yes.
@willemw That probably won't happen as I only have influence on this. If you get any of the others to add that to the "provides", I'll add it here.
How will it work when you try to $ paru -S vscodium
when the package with an exact name exists? Do all the options appear with a default?
Thanks!
@Icelk: Have all related 'vscodium' packages change from 'provide ... codium' to 'provide ... vscodium'.
@willemw So what do you propose we do?
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.