- Arch-dev-public - lists.archlinux.org

News Draft: ppp >= 2.5.0-1 update may require manual intervention
by Felix Yan 14 Sep '23

14 Sep '23

As you may or may not have noticed, both `ppp` and `rp-pppoe` package used to ship a `rp-pppoe.so` and they are not 100% compatible. Back in 2021, ppp 2.4.9 starts to rename its own copy of `rp-pppoe.so` to `pppoe.so`. As of `ppp 2.5.0`, upstream decided to remove the `rp-pppoe.so` symlink and thus broke configurations with the old name. If you still have the old ppp package's `rp-pppoe.so` configured somewhere (likely in /etc/ppp/peers/), please update it to use just `pppoe.so`. Configurations with the same plugin from the `rp-pppoe` package (using full path like /usr/lib/rp-pppoe/rp-pppoe.so) are not affected. -- Regards, Felix Yan

3 3

Arch Linux in August 2023
by Levente Polyak 10 Sep '23

10 Sep '23

## Staff We would like to welcome Tomaz Canabrava (tcanabrava) as part of the Arch Linux Package Maintainer team. ## AURWeb In [AURWeb v6.2.7][0], we primarily focused on bug fixes while revamping Prometheus metrics. We introduced new measures like request tracking and cache-hit/miss ratios for search queries, enhancing our ability to make development decisions and aiding the AUR moderation team in identifying trends. Collaborating with the DevOps team, we introduced a CI/CD feature called [Review Apps][1]. This feature enables us to create virtual machines running AURWeb for each merge request, facilitating change showcases, manual testing, and involving a wider audience for performance, stress-testing, and UI verification. ## RFC We [proposed and accepted an RFC][2] to define the default of not using `PyPI` for Python package sources and only use the platform if there is no other alternative. You can find more details about [this RFC][2] on GitLab. By making this change, we ensure to have a more reliable and less cumbersome default. ## Trademark Policy We've [relocated our Trademark Policy][3] from the Developer area of the ArchWiki to the [service-agreements GitLab repository][4], which is published at [`terms.archlinux.org`][5]. This move centralizes all legal documents, ensuring consistent collaboration across our service agreement materials. [0]: https://gitlab.archlinux.org/archlinux/aurweb/-/tags/v6.2.7 [1]: https://docs.gitlab.com/ee/ci/review_apps/ [2]: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/20 [3]: https://gitlab.archlinux.org/archlinux/service-agreements/-/merge_requests/… [4]: https://gitlab.archlinux.org/archlinux/service-agreements/ [5]: https://terms.archlinux.org/docs/trademark-policy/

1 0

RFC: Add -Wl,-z,pack-relative-relocs
by Jan Alexander Steffens (heftig) 03 Sep '23

03 Sep '23

A new RFC (request for comment) has been opened here: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/23 Please visit the above link for discussion. Summary: Add -Wl,-z,pack-relative-relocs to our LDFLAGS in order to reduce the size of relocations.

1 0

News Draft: ansible-core >= 2.15.3-1 update may require manual intervention
by Robin Candau 17 Aug '23

17 Aug '23

# ansible-core >= 2.15.3-1 update may require manual intervention As of ansible-core version `2.15.3`, upstream moved documentations and examples to a separated [dedicated repository](https://github.com/ansible/ansible-documentation) (see the [related changelogs](https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHAN…) This means that, starting from version `2.15.3` the `ansible-core` package will stop shipping documentations 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: ```sh ansible-config init --disabled > ansible.cfg ``` After updating from ansible-core <= `2.15.2-1` to >= `2.15.3-1`, everyone using a global Ansible configuration file stored under `/etc/ansible/ansible.cfg` will have their configuration saved as a `pacsave` file. To re-instore it, run the following command: ```sh mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg ``` -- Regards, Robin Candau / Antiz

1 2

Arch Linux in July 2023
by Levente Polyak 09 Aug '23

09 Aug '23

## Staff We would like to welcome Mario Oenning (moson) as new Arch Linux Support Staff Member. ## devtools arch-nspawn is now utilizing a distinct scope name instead of the previous `--keep-unit` approach. This allows for the creation of a dedicated scope, placing the container within a slice hierarchy which allows a more precise resource control. This enhancement will be part of the next release. Additionally, we've released version [v1.0.3][0], featuring several enhancements and bug fixes. This version enables the building of unofficial packages containing unsupported architectures and implements measures to ensure the `PKGBUILD` file is version controlled for new repositories. ## gluebuddy Gluebuddy, in its latest release [v0.5.6][1], brings an enhancement by automatically providing tag protection for the entire Arch Linux namespace. This feature ensures that all tags are safeguarded, contributing to the integrity and security of our repositories. ## Bugtracker migration Building upon the successful migration of packaging sources to Git, we are now focused on transferring our bug tracking from Flyspray to GitLab. Our progress can be monitored through [`archlinux/infrastructure#522`][2]. We have made substantial advancements in this process, including the preparation of labels for efficient bug management, the initial implementation of bugbuddy to streamline assignment of maintainers and labels, and a thorough revamp of the Flyspray to GitLab conversion tool `flyspray2gitlab`, with preliminary tests carried out in separate namespaces. # SPI We've completed and submitted the Software in the Public Interest (SPI) [annual project update report for the year 2022][3]. This brief report outlines our achievements, developments, and contributions over the past year. [0]: https://gitlab.archlinux.org/archlinux/devtools/-/releases/v1.0.3 [1]: https://gitlab.archlinux.org/archlinux/gluebuddy/-/commit/be32986196f0268bc… [2]: https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/522 [3]: https://gitlab.archlinux.org/archlinux/project-management/-/issues/10

1 0

NEWS DRAFT: Budgie upgrade requires manual intervention
by arch＠serebit.com 04 Aug '23

04 Aug '23

When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43 must be replaced with magpie-wm, which currently depends on mutter. As mutter43 conflicts with mutter, manual intervention is required to complete the upgrade. First, remove mutter43 via "pacman -Rdd mutter43", then immediately perform the upgrade via "pacman -Syu". Do not relog or reboot between these steps. This will bypass the conflict.

2 1

Mailing list arch-commits
by Leonidas Spyropoulos 28 Jul '23

28 Jul '23

Hello, The arch-commits ML is back with diffs from Gitlab Packages group. Subscribe as normal from https://lists.archlinux.org State repo is not included. No archive is kept. Cheers, -- Leonidas Spyropoulos Developer & DevOps PGP: 59E43E106B247368

1 0

RFC Final Comment Period: Sources for Python packaging
by David Runge 28 Jul '23

28 Jul '23

An RFC has now entered Final Comment Period. In 14 days, discussion will end and the proposal will either be accepted, rejected or withdrawn: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/20 Please visit the above link for discussion. Summary: Default to not using PyPI for Python package sources and only use the platform if there is no other alternative.

1 0

systemd: 254rc2 -> 253.7 -> 254rc3
by Christian Hesse 20 Jul '23

20 Jul '23

Hello everybody, we already had a pre-release of systemd in out testing repositories when I was surprised with another bugfix release in stable branch. Thus pulling the pre-release (254rc2-1) for now, and pushing 253.7-1. Once that is signed-off (please do!) and moved we can continue with pre-releases - probably 254rc3. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}

1 0

Arch Linux in June 2023
by Levente Polyak 15 Jul '23

15 Jul '23

## packaging We have now enabled all packagers to have default access to the multilib and unstable desktop (GNOME/KDE) repositories. This decision removes artificial gates and simplifies the process for packagers to contribute to different aspects of the distro's packaging. By granting wider access by default, we encourage easier participation and collaboration within our distro packaging team. ## devtools We released version `v1.0.3` of devtools which focused on bug fixes. This release addresses the issue of broken packaging repos for newly added packages by ensuring that the actual PKGBUILD is always version controlled. Additionally, we implemented the functionality to skip unofficial architectures, providing better support for building AUR packages with `pkgctl`. ## arch-boxes Starting with the `v20230601` release, arch-boxes images now include x64 UEFI support in addition to legacy BIOS. The GRUB boot loader is used for both UEFI and BIOS systems, ensuring a consistent implementation across different hardware configurations. This is a great enhancement that allows using arch-boxes images on UEFI-based systems. ## ArchISO In the `archlinux-2023.06.01-x86_64.iso` release, the mDNS responder of systemd-resolved is now enabled by default. This improvement enhances the user experience by simplifying network connections during the installation process. This enables convenient connectivity to the live environment via SSH from the local network without the need to know the IP address. Users can simply use the mDNS hostname `archiso.local`. The ArchWiki article ["Install Arch Linux via SSH"][0] has been updated to include a helpful tip with the appropriate command. ## container images Arch Linux's container images are now published to multiple registries. In addition to DockerHub, the images are also pushed to [Quay.io][1] and [GitHub Container registry][2]. This wider distribution ensures availability of the image across multiple platforms and helps mitigate the risk of a single point of failure. Users can now access the Arch Linux container images from their preferred registry, offering greater flexibility and redundancy. ## Specification effort for .BUILDINFO files With the [alpm-buildinfo][3] project, a Rust-based specification effort for the `.BUILDINFO` files found in ALPM packages has been started. The implementation for version 1 of the file is currently in review. [0] https://wiki.archlinux.org/title/Install_Arch_Linux_via_SSH#On_the_local_ma… [1] https://quay.io/repository/archlinux/archlinux [2] https://github.com/archlinux/archlinux-docker/pkgs/container/archlinux [3] https://gitlab.archlinux.org/archlinux/alpm/alpm-buildinfo

1 0