RepoJournal
Arch Linux

@archlinux

The Arch Linux org — the rolling distro and the developers who run it

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Sun 24 may
  21. Mon 25 may
  22. Tue 26 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

BUILDBTW EXECUTOR SHIPS WITH NEW GITLAB RUNNER INFRASTRUCTURE

By RepoJournal · Filed · About Arch Linux

Arch Linux shipped the buildbtw-executor as a production OCI artifact, deploying it inside a dedicated GitLab Runner that's now live across the packaging pipeline.

The buildbtw team merged the executor deployment [1] after months of work moving away from plain GitLab artifacts to OCI delivery, a superior mechanism for binary distribution [2]. Two runners are now active: a secure production instance scoped to archlinux/packaging that runs only protected branches, and a staging runner open to forks and non-protected pipelines. This infrastructure shift closes a long-standing gap in the build system [1]. Alongside the executor rollout, bumpbuddy picked up a new GitLab SSH host key environment variable for arch-pkg-repo-updater [3], and buildbtw itself tightened its release builds by denying compiler warnings and adding demo data to the UI [4][5]. The executor OCI artifact now carries a main tag for easier consumption [6]. Core packages moved steadily: bash landed 5.3.15-1 in testing [7], pacman-mirrorlist refreshed its mirror list [8], and xet-core bumped to 1.5.1-1 [9]. Repository maintenance continued with aurweb's cgit cache getting a tmpfiles.d override to ensure proper cleanup [10].

Action items

References

  1. [1] Merge branch 'add-buildbtw-executor' into 'main' archlinux/infrastructure
  2. [2] Deploy buildbtw-executor inside a new GitLab Runner archlinux/infrastructure
  3. [3] bumpbuddy: Add new arch-pkg-repo-updater GitLab SSH Host Key environment variable archlinux/infrastructure
  4. [4] Merge branch 'add-demo-data-to-bbtw-show-in-release-builds' into 'main' archlinux/buildbtw
  5. [5] Deny warnings in release build archlinux/buildbtw
  6. [6] Merge branch 'main-tag-artifact' into 'main' archlinux/buildbtw
  7. [7] update bash to 5.3.15-1 in core-testing-x86_64 archlinux/state
  8. [8] update pacman-mirrorlist to 20260610-1 in core-testing-any archlinux/state
  9. [9] update xet-core to 1.5.1-1 in extra-x86_64 archlinux/state
  10. [10] aurweb: set tmpfiles.d override for cgit cache archlinux/infrastructure

FAQ

What changed in Arch Linux on June 10, 2026?
Arch Linux shipped the buildbtw-executor as a production OCI artifact, deploying it inside a dedicated GitLab Runner that's now live across the packaging pipeline.
What should Arch Linux teams do about it?
Verify buildbtw-executor is running in your GitLab Runner instances • Test packaging builds against the new secure/staging runner split • Update any local buildbtw references to use the 'main' OCI tag
Which Arch Linux repositories shipped on June 10, 2026?
archlinux/infrastructure, archlinux/buildbtw, archlinux/state

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.