It's probably some weird issue with yaourt. Submit a bug report to yaourt's repo.
Though it might actually be archived, i dont remember. I'd recommend switching to yay personally
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: | 328 |
Popularity: | 7.77 |
First Submitted: | 2020-09-23 18:58 (UTC) |
Last Updated: | 2025-04-16 19:00 (UTC) |
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 Next › Last »
It's probably some weird issue with yaourt. Submit a bug report to yaourt's repo.
Though it might actually be archived, i dont remember. I'd recommend switching to yay personally
@sperg512 this really worked. I'll have it in my mind the next time. Still, I can't understand why I couldn't install it the usual way...
@teras builds fine for me, try directly cloning and running makepkg -si
.
When I try to install this package, I get this error
/tmp/yaourt-tmp-teras/aur-vscodium-bin/./tmp.zpJC22uMc4: line 40: syntax error near unexpected token `('
/tmp/yaourt-tmp-teras/aur-vscodium-bin/./tmp.zpJC22uMc4: line 40: ` cp -r ${srcdir}/!(vscodium-bin.desktop|${pkgname}-${pkgver}.tar.gz) ${pkgdir}/usr/share/${pkgname}'
==> ERROR: Failed to source /tmp/yaourt-tmp-teras/aur-vscodium-bin/./tmp.zpJC22uMc4
Unable to read PKGBUILD
any idea?
Okay, I see. Thanks for letting me know and have a good time with FreeBSD!
I disowned cause I no longer use Arch, I just switched to FreeBSD, before that I was using void so I've been a bit slow before but now I don't even have pacman to test
Does anyone know why @ckatri just updated it to 1.51.0 then disowned? I haven't found a way to contact him about it and ask.
For impatient folk, 1.51.0 builds fine by changing pkgver
to 1.51.0, and updating the relevant sha256sum to the upstream one for your architecture.
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.