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

OpenSSL 3.1 Update
by Pierre Schmitz 10 Jun '23

10 Jun '23

Hi all, I am about to push version 3.1 of OpenSSL into the core-testing repository. This time it is an actual minor update which is compatible with 3.0. That means there is no soname change and no rebuild should be required. However, packages might do runtime checks and ask for the specific version they were built with. OpenSSH is such a case. So far I have not noticed any other package having this check, but I guess we have to figure this out in [testing]. If you notice an issue, please let me know so I can add it to the todo list: https://archlinux.org/todo/openssl-31/ Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com

2 3

NEWS DRAFT: OpenBLAS >= 0.3.23-2 update requires manual intervention
by Felix Yan 05 Jun '23

05 Jun '23

The openblas package prior to version 0.3.23-2 doesn't ship optimized LAPACK routine and CBLAS/LAPACKE interfaces for compatibility. This decision has been reverted now, and the ability to choose a different default system BLAS/LAPACK implementation while keeping openblas installed is now provided to allow future co-installation of BLIS, ATLAS, etc. The default BLAS implementation will be used for most packages like NumPy or R. Please install "blas-openblas" and "blas64-openblas" to make OpenBLAS the default BLAS implementation, just like the old behavior. Unfortunately you will get errors on updating if you currently have OpenBLAS installed as the default BLAS implementation: error: failed to prepare transaction (could not satisfy dependencies) :: installing openblas (0.3.23-2) breaks dependency 'blas' required by cblas :: installing openblas (0.3.23-2) breaks dependency 'blas' required by lapack Please append your preferred default BLAS implementation to the regular -Syu command line to get around it. For example: # pacman -Syu blas-openblas or # pacman -Syu blas -- Regards, Felix Yan

1 0

Git migration completed
by Levente Polyak 03 Jun '23

03 Jun '23

We are proud to announce that the migration to Git packaging succeeded! 🥳 Thanks to everyone who has helped during the migration! Package sources are now available on GitLab[0]. Note that the bugtracker is still flyspray[1] and that merge requests are not accepted as of now. We intend to open the issue tracker and merge requests on the Gitlab package repos in the near future. Mirrors are syncing again, but it may take a bit of time until your mirror of choice has caught up. ## For users Update your system and merge the pacman pacnew `/etc/pacman.conf.pacnew` file. This is required as we have moved the `[community]` repository into `[extra]`. $ pacman -Syu "pacman>=6.0.2-7"` For users of the now deprecated `asp` tool, you will need to switch to `pkgctl`: $ pacman -Syu "devtools>=1:1.0.0-1" $ pkgctl repo clone linux For some more detailed instructions on how to obtain PKGBUILDs see the corresponding wiki article[2]. ## For packagers Before starting, first uninstall `devtools-git-poc` and remove any repos from your filesystem that you cloned during the git proof-of-concept testing. Make sure you have both, an updated devtools and pacman on your system: $ pacman -Syu "devtools>=1:1.0.0-1" "pacman>=6.0.2-7"` Additionally clean up old chroots in `/var/lib/archbuild/` $ rm -rf /var/lib/archbuild/ # or optionally, use the --clean option for pkgctl build *ONCE* $ pkgctl build --clean For instruction on how to use `pkgctl`, please take a look at the "How to be a packager" wiki article[3] and also consult the man page of each subcommand for further information: $ man pkgctl-build $ man pkgctl-repo-clone [0] https://gitlab.archlinux.org/archlinux/packaging/packages [1] https://bugs.archlinux.org [2] https://wiki.archlinux.org/title/Arch_build_system#Retrieve_PKGBUILD_source [3] https://wiki.archlinux.org/title/DeveloperWiki:HOWTO_Be_A_Packager

2 1

Flyspray migration plan
by Jelle van der Waa 02 Jun '23

02 Jun '23

Hey all, We discussed shutting down flyspray during the DevOps meeting. The plan is to migrate all open issues to Gitlab and close them on Flyspray with a comment to the newly created Gitlab issue. All closed bugs will be archived and will most likely become available on https://bugs-old.archlinux.org/ Before we start a migration, we need some time to write a migration script. We would really appreciate it if all packagers can verify if their open bugs are still valid, can be fixed or closed. All packagers (previously known as TU) have been granted access to the Arch Linux project so can assign/close and resolve issues. As of writing we have: Arch Linux: 1072 open tasks Community: 851 open tasks On Gitlab, packagers will get auto-assigned on issues for packages they are the maintainer of in Archweb (https://archlinux.org/devel) A bot will periodically scan issues and automatically assign them. We are also looking into creating a generic global issue template for features/bugs. The bot will also set an “unconfirmed” label to new issues so bug wranglers and packagers alike can see and filter whether a bug has already been reproduced. Migrating the issues to Gitlab implies that we will open Gitlab issues for everyone. There is no timeline set yet for the migration, the main blocker is writing a migration script for our open issues. Greetings, Jelle van der Waa

3 2

[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