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

[multilib] access
by Jelle van der Waa 28 May '23

28 May '23

Hey all, I would like to propose to allow everyone to upload to [multilib], currently it's restricted to a small set of packagers. This already caused some confusion because a packager could not upload mangohud. Let's just give everyone access by default. Greetings, Jelle van der Waa

3 2

GitLab bug: Your push has been rejected....
by Kristian Klausen 27 May '23

27 May '23

Hi all, As pointed out by multiple staff at IRC, there is currently a bug in GitLab, resulting in the following error on some git push: remote: ======================================================================== remote: remote: Your push has been rejected, because this repository has exceeded remote: its size limit of 0 Bytes by 25 GB. Please contact your GitLab remote: administrator for more information. remote: remote: ======================================================================== This is a harmless bug in GitLab[1] and the push succeeds. GitLab will fix it eventually. [1] https://gitlab.com/gitlab-org/gitlab/-/issues/409953 Cheers, Kristian Klausen

1 0

FrOSCon 2023
by Jelle van der Waa 22 May '23

22 May '23

Hey all, FrOSCon 2023 has been announced and is held on 5-6 of August. FrOSCon is a small (usually ~ 250) conference near Bonn, Germany. In the past we had devrooms there and hacking sessions. [1] I haven't made plans yet for attending but likely will, it would be nice if we had a small meetup there, hack together on some fun things and enjoy a Kölsch. Is anyone in the team thinking of attending? Greetings, Jelle [1] https://lists.froscon.org/hyperkitty/list/newsletter@lists.froscon.org/thre…

2 1

Git migration started
by Jelle van der Waa 20 May '23

20 May '23

Hi all, I got my morning coffee ready and will now start disabling ssh/svn access and stop our rsync endpoint. For more details of the migration please read the announcement email. [1] [1] https://lists.archlinux.org/archives/list/arch-announce@lists.archlinux.org… Knocking on wood that this all goes smoothly, Jelle

3 3

Git packaging rollout 🚀
by Levente Polyak 17 May '23

17 May '23

Hi everyone! We're excited to announce that the rollout for our Git packaging implementation is scheduled for Friday, May 19th. Please note that packaging and mirror sync will not be possible during the rollout as we'll need to shut down the services. We expect the services to be available and the rollout to be finished on Sunday, May 21th. This release date allows you for 17 more days to test pkgctl and prepare for the announced changes. We highly recommend that you take advantage of this time to ensure a smooth transition to the new implementation. Background information about the changes can be found in the two previous Git packaging threads on arch-dev-public [0][1]. Once the rollout is completed, we'll be sending out email notifications and a news entry with precise instructions and information for packagers as well as users. The primary feature and rollout owners are Foxboron and me (anthraxx). We will also be available to provide extended help and guidance to ensure that everyone can use the new tooling and workflow. Please don't hesitate to reach out to us, we're happy to help in any way we can. A detailed runbook for the whole rollout can be found here [2]. A heavily shortened version roughly looks as follows: ## 1. Pre-Rollout (Thursday 18. May) - news entry and announcement about the downtime - convert all SVN packages to Git repositories - trigger a fresh borg backup (6h) ## 2. Rollout (Friday 19. May) - shut down mirror and packaging services - update all changed package repositories - setup the new repo layout - import the pacman database state into a Git repository - deploy the new dbscripts version - release new devtools and pacman packages - deploy archweb and security-tracker ## 3. Validation (Saturday 20. May) - test the complete packaging workflow - test archweb and security-tracker features - hand out access to early access packagers ## 4. Opening (Sunday 21. May latest) - restart mirror and packaging services - send news post with detailed instructions - Party time Cheers [0] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… [1] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… [2] https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g

2 2

Git migration announcement
by Jelle van der Waa 15 May '23

15 May '23

This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period. Notification when the migration starts, and when it is completed, will be published on the [arch-dev-public] mailing list. # How does this impact Arch Linux users? The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration. All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before. Note: After the migration is done, users that have the testing repositories enabled need to include the new repositories ([core-testing] and [extra-testing] instead of [testing]) in their pacman.conf before updating their system. Other changes: - SVN access is discontinued and will disappear. [1] - The svn2git mirror will no longer be updated. - asp, which relies on the svn2git mirror, will stop working. It is replaced by pkgctl repo clone. [2] # How does this impact Arch Linux tier 1 mirrors? During the migration rsync and HTTP access will be shut down. We will send an email notification to arch-mirrors once everything has been finished. # How does this impact Arch Linux packagers? Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration. [1] https://archlinux.org/svn/ [2] https://lists.archlinux.org/archives/list/arch-mirrors@lists.archlinux.org/

1 0

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

07 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

Python 3.11 in [staging]
by Jelle van der Waa 29 Apr '23

29 Apr '23

Early Easter suprise, After some delay Python 3.11 rebuilds are happening in [staging], so please don't start any rebuild. Thanks to felixonmars for starting and rebuilding! Thanks, Jelle van der Waa

4 3