[arch-announce] Increasing the default vm.max_map_count value
The [vm.max_map_count][1] paramater will be increased from the default `65530` value to `1048576`. This change should help address performance, crash or start-up issues for a number of memory intensive applications, particularly for (but not limited to) [some Windows games][2] played through Wine/Steam Proton. Overall, end users should have a smoother experience out of the box with no expressed concerns about potential downsides in [the related proposal on arch-dev-public mailing list][3]. This `vm.max_map_count` increase is introduced in the `2024.04.07-1` release of the [filesystem package][4] and will be effective right after the upgrade. Before upgrading, in case you are already setting your own value for that parameter in a `sysctl.d` configuration file, either remove it (to switch to the new default value) or make sure your configuration file will be read [with a higher priority][5] than the `/usr/lib/sysctl.d/10-arch.conf` file (to supersede the new default value). [1]: https://docs.kernel.org/admin-guide/sysctl/vm.html#max-map-count [2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057792/comments/5 [3]: https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/ [4]: https://archlinux.org/packages/core/any/filesystem/ [5]: https://man.archlinux.org/man/sysctl.8#SYSTEM_FILE_PRECEDENCE URL: https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/
[arch-announce] ansible-core >= 2.15.3-1 update may require manual intervention
As of `ansible-core 2.15.3`, upstream moved documentation and examples to a separate [dedicated repository](https://github.com/ansible/ansible-documentation) (see the [related changelogs](https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHANGELOG-v2.15.rst#minor-changes)). This means that, starting from version `2.15.3` the `ansible-core` package will stop shipping documentation and a default configuration example under `/etc/ansible/ansible.cfg`. Regarding the documentation, it is available online: https://docs.ansible.com/; As for the configuration file, as explained in the [wiki](https://wiki.archlinux.org/title/Ansible#Configuration), a base config can be generated with the following command: ``` ansible-config init --disabled ansible.cfg ``` After updating from `ansible-core` = `2.15.2-1` to = `2.15.3-1`, everyone using a **custom** global Ansible configuration file stored under `/etc/ansible/ansible.cfg` will have their configuration saved as a `pacsave` file. To restore it, run the following command: ``` mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg ``` URL: https://archlinux.org/news/ansible-core-2153-1-update-may-require-manual-intervention/
[arch-announce] Switch to the base-devel meta package requires manual intervention
The `base-devel` package group has recently been replaced by a meta package of the same name. People that had the `base-devel` package group installed (meaning people that installed `base-devel` before February 2nd) have to explicitly re-install it to get the new `base-devel` package installed on their system: ``` pacman -Syu base-devel ``` URL: https://archlinux.org/news/switch-to-the-base-devel-meta-package-requires-manual-intervention/
