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

SIGNSTAR TEARS DOWN STATE COMPARISON LAYER IN MAJOR REFACTOR

By RepoJournal · Filed · About Arch Linux

Arch's signing infrastructure is simplifying its state handling system, removing the legacy StateHandling mechanism in favor of a cleaner StateDiff approach.

The signstar project shipped a breaking refactor [1] that eliminates StateHandling-based state comparison, a move that streamlines how the system tracks configuration changes. Paired with this, NetHsmConfigState got renamed to NetHsmConfigStateLegacy [2] as the deeper entanglement with StateHandling made direct migration impossible. The team is laying groundwork for the next generation with three new feature commits: SystemUserData tracking [3] to categorize different kinds of system users, a ConfigSystemUserData trait [4] to expose that data to configs, and SystemUserId::root [5] as a convenience method for root access. On the package side, the Erlang ecosystem continues its steady march through staging: ejabberd 26.04-2 [6], elixir 1.19.5-2 [7], and rebar3 3.27.0-2 [8] are all queued for promotion, alongside Haskell library updates for ranged-sets [9] and fgl [10].

Action items

References

  1. [1] refactor!: Remove `StateHandling` based state comparison archlinux/signstar
  2. [2] refactor: Rename `NetHsmConfigState` to `NetHsmConfigStateLegacy` archlinux/signstar
  3. [3] feat: Add `SystemUserData` to track the different kinds of system users archlinux/signstar
  4. [4] feat: Add `ConfigSystemUserData` trait returning `SystemUserData` archlinux/signstar
  5. [5] feat: Add `SystemUserId::root` to return the root user archlinux/signstar
  6. [6] update ejabberd to 26.04-2 in extra-staging-x86_64 archlinux/state
  7. [7] update elixir to 1.19.5-2 in extra-staging-any archlinux/state
  8. [8] update rebar3 to 3.27.0-2 in extra-staging-any archlinux/state
  9. [9] update haskell-ranged-sets to 0.5.0-95 in extra-staging-x86_64 archlinux/state
  10. [10] update haskell-fgl to 5.8.3.0-125 in extra-staging-x86_64 archlinux/state

FAQ

What changed in Arch Linux on May 24, 2026?
Arch's signing infrastructure is simplifying its state handling system, removing the legacy StateHandling mechanism in favor of a cleaner StateDiff approach.
What should Arch Linux teams do about it?
Review StateHandling removal if you maintain dependent code • Prepare for NetHsmConfigStateLegacy deprecation timeline • Test Erlang ecosystem updates before general release
Which Arch Linux repositories shipped on May 24, 2026?
archlinux/signstar, 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.