Arch Linux in October 2023
## Staff We would like to welcome [Christian Heusel (gromit)][0] to the Arch Linux DevOps team, expanding his responsibilities. ## bugbuddy The initial version of [Bugbuddy][1], our GitLab bug bot, has been introduced. This tool assigns package maintainers to confirmed GitLab issues in the packaging group. Notably, the code has undergone substantial improvement, now operating as a daemon process that can promptly respond to GitLab webhook calls. ## dbscripts The `db-remove` command has been streamlined, eliminating the need to pass an `arch` parameter by adding automatic resolution. Moreover, the `db-update` command now properly checks staged packages against staging/testing, addressing a loophole that previously caused state inconsistencies. Additionally we've enhanced the development process by parallelizing test execution, massively reducing unit testing duration. ## RFC In late 2021, an [RFC was proposed][2] to rename the `Trusted User` role to `Package Maintainer`, aligning it with the role's evolving nature within the Arch staff. The RFC, voted positively in late 2022, has now resulted in the successful renaming across various Arch resources, including the [Packaging Bylaws][3], [ArchWeb][4], [AURWeb][5], [ArchWiki][6], and the "[What can I do for Arch Linux?][7]" page. ## ArchWiki The [ArchWiki has been updated to MediaWiki 1.40][8], necessitating adjustments to the ArchLinux extension due to upstream changes in the Vector 2022 skin. This has prompted consideration of [switching to the Timeless skin][9]. Additionally, there has been a switch from PNG to SVG images in the wiki for article status templates and statistic histograms. The wiki now features the addition of [Extension:Thanks][10] and [Extension:DiscussionTools][11], offering users a streamlined way to express gratitude and heavily simplifying discussions on talk pages. ## ArchISO The ISO now provides a `/boot/grub/loopback.cfg` file which GRUB and Super GRUB2 Disk users can use to boot the ISO file without needing to manually specify the kernel, initrd and kernel command line parameters. Documentation on utilizing the `loopback.cfg` file is available both [upstream][12] and on [ArchWiki][13]. [0]: https://lists.archlinux.org/hyperkitty/list/arch-devops@lists.archlinux.org/... [1]: https://gitlab.archlinux.org/archlinux/bugbuddy/ [2]: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/7 [3]: https://gitlab.archlinux.org/archlinux/package-maintainer-bylaws/-/merge_req... [4]: https://github.com/archlinux/archweb/pull/478 [5]: https://gitlab.archlinux.org/archlinux/aurweb/-/merge_requests/755 [6]: https://wiki.archlinux.org/index.php?title=ArchWiki_talk:Requests&oldid=790989#Trusted_User_name_change [7]: https://gitlab.archlinux.org/archlinux/neoasknot/-/merge_requests/84 [8]: https://gitlab.archlinux.org/archlinux/infrastructure/-/merge_requests/747 [9]: https://github.com/archlinux/archwiki/pull/71 [10]: https://www.mediawiki.org/wiki/Extension:Thanks [11]: https://www.mediawiki.org/wiki/Extension:DiscussionTools [12]: https://www.supergrubdisk.org/wiki/Loopback.cfg [13]: https://wiki.archlinux.org/title/Multiboot_USB_drive#Arch_Linux_monthly_rele...
participants (1)
-
Levente Polyak