| 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.20 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2024-11-16 02:00 (UTC) |
@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?
A specific 'provide' name in several packages will give you all the provide choices:
$ paru -S codium
:: Resolving dependencies...
:: There are 3 providers available for codium:
:: Repository AUR:
1) vscodium-git 2) vscodium 3) vscodium-bin
Enter a number (default=1):
Normally, you would search on 'vscodium' instead of (the unknown) 'codium' (name), but that will now not give you all the 'provide' choices:
paru -S vscodium
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...
Repo Make (3) gulp-4.0.2-3 yarn-1.22.17-1 git-lfs-3.0.1-1
Aur (2) nvm-0.39.0-1 vscodium-1.61.2-1
:: Proceed to review? [Y/n]:
@willemw Thanks. It should now be fixed.
@Icelk:
...
looking for conflicting packages...
Packages (1) vscodium-bin-1.61.2-3
Total Installed Size: 268.72 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################] 100%
(1/1) checking package integrity [#####################################################################] 100%
(1/1) loading package files [#####################################################################] 100%
(1/1) checking for file conflicts [#####################################################################] 100%
error: failed to commit transaction (conflicting files)
vscodium-bin: /usr/bin/codium exists in filesystem (owned by vscodium)
vscodium-bin: /usr/bin/vscodium exists in filesystem (owned by vscodium)
vscodium-bin: /usr/share/pixmaps/vscodium.png exists in filesystem (owned by vscodium)
Errors occurred, no packages were upgraded.
The issue should now be resolved.
Regarding the conflict, the wiki states that we don't need to specify a conflict when we have a provides in common.
Edit pkgbuild as follows:
pkgrel=3
sha256sums=('65e6b053e6d8be61763801312ded64a82cf835d77a6eabe1b9d7eb9e87b2e49b'
'f26703924abca3738f2e1f84e5a1e27e8cc7dae4364bb53dbff03c2de5fe0898')
source=('vscodium-bin.desktop'
'vscodium-bin-uri-handler.desktop')
Yeah having the same issue
Building vscodium-bin...
==> Making package: vscodium-bin 1.61.2-2 (Wed 27 Oct 2021 03:01:32)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found vscodium-bin.desktop
-> Found VSCodium-linux-x64-1.61.2.tar.gz
==> Validating source files with sha256sums...
vscodium-bin.desktop ... Passed
==> Validating source_x86_64 files with sha256sums...
VSCodium-linux-x64-1.61.2.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting VSCodium-linux-x64-1.61.2.tar.gz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/var/tmp/pamac-build-corey/vscodium-bin/src/vscodium-bin-uri-handler.desktop': No such file or directory
==> ERROR: A failure occurred in package().
Aborting..
FYI vscodium-bin-uri-handler.desktop needs to be added to the source section section in pkgbuild
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.