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 . Note that the bugtracker is still flyspray 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 .

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 and also consult the man page of each subcommand for further information:

$ man pkgctl-build$ man pkgctl-repo-clone

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 dissappear.
• 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 .

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.