Arch Linux User Repository

@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.

Hi @icelk, thanks for your reply.

I'm sorry; it was something yay cache-related. It confused me that I received this error even after choosing a clean build. I decided to clean the cache entries manually, and now it works like a charm.

Thank you for your work!

@nervocalm

Hi! I think you maybe need to update your rust. If youve installed it with rustup, run rustup update

Hi guys!

I am getting a rust error in the last build.

info: component 'rust-std' for target 'x86_64-unknown-linux-gnu' is up to date
+++ cargo build --release --target x86_64-unknown-linux-gnu --bin=code
error: rustc 1.86.0 is not supported by the following packages:
  time@0.3.47 requires rustc 1.88.0
  time-core@0.1.8 requires rustc 1.88.0
Either upgrade rustc or select compatible dependency versions with
`cargo update <name>@<current-ver> --precise <compatible-ver>`
where `<compatible-ver>` is the latest version supporting rustc 1.86.0

++++ error_function build
++++ ((  ! BASH_SUBSHELL  ))
+++++ gettext 'A failure occurred in %s().'
++++ error 'A failure occurred in %s().' build
++++ local 'mesg=A failure occurred in %s().'
++++ shift
+++++ gettext ERROR:
++++ printf $'\E[1m\E[31m==> ERROR:\E(B\E[m\E[1m A failure occurred in %s().\E(B\E[m\\n' build
==> ERROR: A failure occurred in build().

Initially it download the rust 1.86 package

info: using existing install for 'stable-x86_64-unknown-linux-gnu'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.86.0 (05f9846f8 2025-03-31)

RELEASE_VERSION="1.110.01571"
MS_TAG="1.110.0"
MS_COMMIT="0870c2a0c7c0564e7631bfed2675573a94ba4455"

But then time and time-core packages require rust 1.88 at least. Anybody else?

Thanks!

@Gianfilippo980 I have !debug set in my own /etc/makepkg.conf anyway, because in my experience those debug packages tend to be problematic anyway (indeed weird conflicts) and their size can also be enormous, wasting a lot of disk space.

They are useful if you actually plan to debug things, but most of the time that's not the case.

@Gianfilippo980 I removed the debug package. @drakkar1969 It's removed. @jronald these are also fixed by removing the debug symbols

There seems to be a compatibility problem between "vscodium-bin-debug" and "teams-for-linux-debug" where they try to own the same files. producing a Pacman error: https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error The files in question are in the following directories:

- /usr/lib/debug/.build-id/84/
- /usr/lib/debug/.build-id/8f/
- /usr/lib/debug/.build-id/be/
- /usr/lib/debug/.build-id/cd/
- /usr/lib/debug/.build-id/d3/
- /usr/lib/debug/.build-id/d6/
- /usr/lib/debug/.build-id/f5/
- /usr/lib/debug/.build-id/f6/

Vscodium now uses Electron version 39 internally, which should automatically default to Wayland. Not sure that the vscodium-bin-wayland.desktop is still needed, on my system Vscodium runs on Wayland whether I launch with vscodium-bin-wayland.desktop or vscodium-bin.desktop

many warnings, full logs for makepkg are too long to paste here, see https://bbs.archlinux.org/viewtopic.php?pid=2279997#p2279997

Here are some logs:

Error while writing index for `/usr/lib/debug/opt/vscodium-bin/chrome-sandbox.debug': No debugging symbols
Error while writing index for `/home/u/Downloads/vscodium-bin/pkg/vscodium-bin/opt/vscodium-bin/chrome-sandbox': No debugging symbols
gdb-add-index: No index was created for ./opt/vscodium-bin/chrome-sandbox
gdb-add-index: [Was there no debuginfo? Was there already an index?]
debugedit: ./opt/vscodium-bin/resources/app/node_modules/node-pty/build/Release/pty.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/node-pty/build/Release/pty.node: Unknown debugging section .debug_gnu_pubtypes
Error while writing index for `/usr/lib/debug/opt/vscodium-bin/resources/app/node_modules/@vscodium/native-keymap/build/Release/keymapping.node.debug': No debugging symbols
Error while writing index for `/home/u/Downloads/vscodium-bin/pkg/vscodium-bin/opt/vscodium-bin/resources/app/node_modules/@vscodium/native-keymap/build/Release/keymapping.node': No debugging symbols
gdb-add-index: No index was created for ./opt/vscodium-bin/resources/app/node_modules/@vscodium/native-keymap/build/Release/keymapping.node
gdb-add-index: [Was there no debuginfo? Was there already an index?]
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@vscodium/policy-watcher/build/Release/vscodium-policy-watcher.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@vscodium/policy-watcher/build/Release/vscodium-policy-watcher.node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/vscodium-bin/resources/app/node_modules/kerberos/build/Release/obj.target/kerberos.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/kerberos/build/Release/obj.target/kerberos.node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/vscodium-bin/resources/app/node_modules/kerberos/build/Release/kerberos.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/kerberos/build/Release/kerberos.node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@parcel/watcher/build/Release/watcher.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@parcel/watcher/build/Release/watcher.node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@vscode/sqlite3/build/Release/vscode-sqlite3.node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/vscodium-bin/resources/app/node_modules/@vscode/sqlite3/build/Release/vscode-sqlite3.node: Unknown debugging section .debug_gnu_pubtypes
Error while writing index for `/usr/lib/debug/opt/vscodium-bin/resources/app/node_modules/@vscode/ripgrep/bin/rg.debug': No debugging symbols
Error while writing index for `/home/u/Downloads/vscodium-bin/pkg/vscodium-bin/opt/vscodium-bin/resources/app/node_modules/@vscode/ripgrep/bin/rg': No debugging symbols

Coexistence of vscdoium(x11) and vscdoium(wayland) is a little annoying. Is there anyway to make it wayland only, for desktop entries, file manager context menu, etc?

Strangely this package doesn't provide Plasma 6 global menu while AUR package 'vscodium' does.