Admin message
Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.
<!--
Please read our Bug reporting guidelines before opening a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
If you want to help catching more bugs upfront, consider joining the Arch Testing Team:
https://wiki.archlinux.org/title/Arch_Testing_Team
-->
# Description:
We are facing quite a big issue with the following commit:
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a
To the version:
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/blob/6.0.2-9/makepkg.conf?ref_type=tags
First, I would like to ask what led you to this change for the default modification of this config file to enable `debug` for end-users?
However, a far more extensive problem is this change to the zstd parameters:
`COMPRESSZST=(zstd -c -T0 --ultra -20 -)`
On all servers and desktops with Arch, updates now take 10-20 times longer than before in the "Compressing package..." section. Setting the compression ultra level to 20, excuse the word, is something only a "fool" would do. Nowadays, disk space is not the issue, but the speed of production systems is. Do you conduct any stress tests before making such a crucial default parameter change?
Of course, I will set the configuration according to my preferences, but these are the default parameters. Moreover, the given file overwrote the original file, without creating the standard `.pacnew`.
Please consider and thoroughly test such future changes from a system performance perspective. This problem has taken up quite a bit of our time. Thank you for resolving it and, more importantly, avoiding such mistakes in the future. Thank you.
# Additional info:
* package version(s): >=6.0.2-9
* config and/or log files: /etc/makepkg.conf
# Steps to reproduce:
<!-- Describe how to reproduce the bug step by step including the commands -->
Run AUR update...