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

Arch Linux in April 2023
by Levente Polyak 08 May '23

08 May '23

## project management We've create a GitLab Board [0] to track all tasks related to project management and project leadership. This Board allows us to visualize the exact state of tasks using different lanes and labels, making it easier to keep track of ongoing progress. Additionally, tasks will receive comments and lane updates to reflect the latest developments. This is another step towards providing increased transparency, structure, and visibility for our staff and users alike. The Board will continuously include an issue for next month's monthly report pad, streamlining the process for staff to add noteworthy bulletpoints about their progress. ## RFC We proposed and accepted an RFC to change our packaging build flags from _FORTIFY_SOURCE=2 to _FORTIFY_SOURCE=3 for better fortification coverage. Once rolled out, this change provides enhanced buffer size detection and improves the overall fortification coverage. You can find more details about this RFC on GitLab [1]. By making this change, we will be able to further strengthen the security of our distro and better protect our users. ## infrastructure We've set up an official crates.io service account [2] and assigned ownership of relevant projects such as various alpm and arch-audit related crates. This allows us to better manage and control access. In the future we will be able to use this service account to extend release automation via GitLab. ## Python This month we've focused on the Python ecosystem and have successfully upgraded the Python interpreter and relevant packages to version 3.11. As part of this process, we've rebuilt all packages that were dependent on Python and have fixed numerous issues in the process. We're pleased to report that we've completed these upgrades by the end of April and have since moved all relevant packages over to our binary repositories. ## Docker We applied and were accepted into the Docker-Sponsored Open Source Program with our Arch Linux organization. In addition to the monthly updated Docker Official Images, being part of this program provides us with several benefits for the images distributed through our organization. One of the key benefits is that users pulling public images from our project namespace will receive access to unlimited pulls and unlimited egress. [0] https://gitlab.archlinux.org/archlinux/project-management/-/boards [1] https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17 [2] https://crates.io/users/archlinux-github

1 0

dropping retired X.Org Packages
by Andreas Radke 04 May '23

04 May '23

Following this reminder post[1]+[2] I'm going to remove the following packages soon from the repos: xf86-input-elographics xf86-input-synaptics xf86-input-vmmouse xf86-input-void Any objections? -Andy [1]https://lore.kernel.org/distributions/1ea25603-171c-062e-bc02-bcdfc3acd01… [2]https://gitlab.freedesktop.org/xorg/doc/xorg-docs/-/blob/master/MAINTAINE…

2 2

Call for participation: Git packaging POC 🚀🎉
by Morten Linderud 01 May '23

01 May '23

Hi everyone! Levente and I have been busy preparing a test environment for the new git package workflow, which is going to replace the svn repository. To test the new git package setup install `devtools-git-poc` from the [community] repository and use the new `pkgctl` utility. Please check each time if there is a new upgrade before playing around. The goal of the testing is to figure out UX issues, bugs and larger issues that would need to be dealt with before a git migration can happen. It's therefor very important that people sit down and play around with the tools :) Support and feedback will be dealt with in the #archlinux-projects channel. Report bugs in GitLab with the following additional information: - devtools-git-poc package version - full PKGBUILD or pkg repo including the Git hash - terminal input and output The workflow should be the following: Basic setup ----------- ### setup packager Make sure your personal `makepkg.conf` contains your packager identity and gpg key. ### authenticate to gitlab pkgctl auth maintain existing packages -------------------------- ### clone an existing package pkgctl repo clone existing-package ### build a package pkgctl build ### release a package pkgctl release pkgctl db update ### combined UX The last three steps can also be expressed as: pkgctl build --release --db-update ### rebuild into staging vim PKGBUILD pkgctl build --staging pkgctl release --staging pkgctl db update This can be completely condensed by: pkgctl build --rebuild --staging --release --db-update maintain new packages --------------------- ### create a new package repo without history pkgctl repo create new-pkgbase pkgctl repo clone new-pkgbase ### add existing AUR repo cd packagerepo pkgctl repo create pkgctl repo configure ### first official build/release Specify the target repo on first run, as the tool can't know it's destination automatically yet pkgctl build --repo extra pkgctl release --repo extra --db-update --- The packages are uploaded into a test group here: https://gitlab.archlinux.org/bot-test/packages This test also includes junior developer and junior packagers. They can only push packages into staging and testing, and not release into the stable repositories. We currently have a couple of people with these permissions to try and figure out issues on that part of the setup. If anyone is interested helping out on this please reach out on the #archlinux-projects IRC channel on Libera. Background on the changes can be found here: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… Cheers!

6 8