























If you're upgrading from previous version, you need to manually remove millennium and its python-i686-bin dependency. Then, you can install the latest version including the new lib32-python311-bin dependency.
May I ask you again to remove the debug option? There's no reason for this package to override the user preference.
-- The C compiler identification is GNU 16.1.1 -- The CXX compiler identification is GNU 16.1.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done
-- [MLNM] Configuring dependencies... -- [MLNM] Version: v3.1.0 -- [MLNM] Commit OID: 76f9012b6ac14c454cfe3d4ad726ebddccff16e7 -- Configuring done (6.3s) -- Generating done (0.2s) -- Build files have been written to: /tmp/localadmin-cache/yay/millennium/src/Millennium/build [0/2] Re-checking globbed directories... [531/577] Building CXX object src/CMakeFiles/Millennium.dir/bindings/theme_cfg.cc.o
Caution: The application „/usr/bin/bash“ has crashed.
Just using options=(debug) without declaring millennium-debug in pkgname means the debug package gets built but never installed - it just sits in your AUR helpers clone directory and gets cleaned up.
Then this is a configuration issue with your AUR helper. makepkg and any sensible AUR helper (like aurutils) respects the debug option. Brute-forcing debug package creation is not the right way.
We need it as a proper split package, this seems to be the standard approach.
There are very few constellations where this could be necessary, and it's definitely not the standard approach or needed here.
Could you please remove the debug option? This overrides the global option from /etc/makepkg.conf. Users who disable debug package creation are doing this deliberately and I see no reason to ignore this preference.
@Coelacanthus tried it again, doesn't work the way we need it. The debug symbols need to actually be installed to /usr/lib/debug/ so coredumpctl gdb can pick them up for proper back-traces when millennium or plugins crash. Just using options=(debug) without declaring millennium-debug in pkgname means the debug package gets built but never installed - it just sits in your AUR helpers clone directory and gets cleaned up. We need it as a proper split package, this seems to be the standard approach. I'm open to suggestions though, I definitely don't know everything about there is to know about the AUR.
If you want to continue the conversation, create an issue on the GitHub. Cheers.
@shdwmtr git is a make dependency which missing, this missing dependency fails the chroot builds:
[2026-03-25T20:33:06.506Z] ==> Making package: millennium 3.0.0_beta.16-1 (Thu Mar 26 00:33:06 2026)
[2026-03-25T20:33:06.515Z] ==> Retrieving sources...
[2026-03-25T20:33:06.519Z] -> Cloning Millennium git repo...
[2026-03-25T20:33:06.529Z] Cloning into bare repository '/tmp/tmpozynarsj/Millennium'...
[2026-03-25T20:33:12.090Z] ==> Validating source files with sha256sums...
[2026-03-25T20:33:12.147Z] Millennium ... Skipped
[2026-03-25T20:33:16.076Z] ==> ERROR: Cannot find the git package needed to handle git sources.
bun install failed cannot install on cachyos
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。
NOTE (Mar 16 2026): As of millennium 3.0.0_beta.1 python plugins are not supported. At the time of writing this, Extendium is the only plugin that has not been ported to Lua. However, you can find dev builds on their repository that are compatible with Lua.