@BryanLiang
Yes I am aware, but where do they come from? I don't see their creation in PKGBUILD. This doesn't seem acute since they are benign(?).
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: | 307 |
Popularity: | 11.08 |
First Submitted: | 2020-09-23 18:58 (UTC) |
Last Updated: | 2024-10-10 19:00 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 23 Next › Last »
@BryanLiang
Yes I am aware, but where do they come from? I don't see their creation in PKGBUILD. This doesn't seem acute since they are benign(?).
@Icelk I go to check the /opt/vscodium-bin after seeing @ZorinArch's comment.
The directory indeed contains multiple broken symbolic links.
Here is the screenshot: https://s2.loli.net/2024/03/22/83WxazUoctL64JD.png
@ZorinArch
The PKGBUILD doesn't contain commands to link them; at least I'm not seeing it. Please point me in the right direction.
@Icelk, the symlinks inside /opt/vscodium-bin/
do nothing to the app.
@ZorinArch Why?
Hi @Icelk, please add these lines to clean up symlinks from /opt/vscodium-bin/
package() {
....
# Clean Symlinks
find "${pkgdir}/opt/${pkgname}/" -type l -delete
}
@ph14nix no. That seems to be an issue with makepkg: all packages are automatically stripped. Since a month back, the strip command is in the debugedit package. It's the pacman package (which provides makepkg) which should depend on it. We're not explicitly using strip.
@Ranguna
Have you tried installing this package first? Looks like some other package is writing to electron's paths
Can you please add debugedit to build dependencies of this pacakge? Otherwise, it prints errors about command not being found when building package (the build succeds anyway though).
I'm getting the following error when installing, I have electron27-bin as a dependency of another package I use:
vscodium-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6 exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699 exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d.debug exists in filesystem (owned by electron27-bin-debug)
I'm also getting the errors above when attempting to install alongside the vscodium insider bin package.
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.