You are not logged in.
I'm not sure which subform this issue belongs to.
Since a few days I have the following problem with yay and packages from the AUR: It hangs when "compressing" a new package downloaded from the AUR.
Last edited by questionask (2024-02-12 15:48:08)
Offline
Do you have the same issue when just using makepkg?
For local builds, disable compression altogether - you're basically just wasting time de/compressing it: see PKGEXT in https://man.archlinux.org/man/makepkg.conf.5
Edit: also https://wiki.archlinux.org/title/Makepk … algorithms
Last edited by seth (2024-02-11 16:24:18)
Offline
Mod note: Moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Yes, same problem with makepkg, and disabling compression resolves the issue.
Does setting PKGEXT='.pkg.tar' globally also affect yay?
Offline
Does setting PKGEXT='.pkg.tar' globally also affect yay?
I'm really not trying to be a dick - but if you have to ask that, you really shouldn't use yay. Just use makepkg.
Last edited by Trilby (2024-02-11 18:44:13)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
yay is a wrapper around makepkg and pacman and if you don't sufficiently understand the underlying tools, it'll get you into trouble.
The compression might just hang because the to-be-compressed data is use and you're starting to swap since yay also has the stupid habit of unconditionally building everything in /tmp (ie. it doesn't "hang", it just takes a lot of time)
Offline
Thanks! So I set it globally.
Is the compression issue a bug?
Offline
The compression might just hang because the to-be-compressed data is use and you're starting to swap since yay also has the stupid habit of unconditionally building everything in /tmp (ie. it doesn't "hang", it just takes a lot of time)
Maybe check RAM and CPU pressure while it "hangs" and try a small package that won't consume many resources to build.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
building everything in /tmp (ie. it doesn't "hang", it just takes a lot of time)
I've never been able to recover my Linuces over the years, when compilation ate more the actual physical RAM on my computers... (or maybe I had waited too little? Is an "entire afternoon" a short period of time to wait for?)
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
This is due to a change in makepkg.conf: https://gitlab.archlinux.org/archlinux/ … heads#L142, just remove the
--ultra -20
to get the previous behavior.
Additionally it builds debug packages now by default: https://gitlab.archlinux.org/archlinux/ … =heads#L97, prefix
debug
with an exclamation mark to turn it off.
Edit: Spelling
Last edited by Tarqi (2024-02-12 18:48:01)
Knowing others is wisdom, knowing yourself is enlightenment. ~Lao Tse
Offline
this happens with me too but i dint find a fix for it so im ussing makepkg instead
just a normal arch user
Offline