OBLinux Arch Repository Signing Key Update

Some existing OBLinux Arch installations may need a one-time repository signing-key update before they can continue receiving updates from the OBLinux package repository.

Who is affected

This affects some OBLinux Arch installations created before September 24, 2026. New installations from the current OBLinux Arch ISO already include the new signing key and do not need this procedure.

What you might see

When updating your system, you may encounter an error similar to:

error: oblinux_repo: key "F83C29998D979B913298C40E7E0180391C821D13" is unknown

This is the result of an OBLinux repository signing-key update. Your installation does not yet trust the new key the OBLinux package repository is signed with, so Pacman refuses to use it until the key is installed.

What this means for you

• You do not need to reinstall OBLinux.
• Your existing installation, applications, settings, and personal files are unaffected.
• The procedure below only needs to be performed once.

How to update the signing key

Open a terminal and run the following steps in order.

Step 1 — Download the new OBLinux public key

curl -fL \
  https://raw.githubusercontent.com/marcoobaid/oblinux-arch-iso/main/airootfs/usr/share/pacman/keyrings/oblinux-repo.gpg \
  -o /tmp/oblinux-repo.gpg

Step 2 — Verify the key fingerprint before trusting it

gpg --show-keys --with-fingerprint /tmp/oblinux-repo.gpg

The fingerprint in the output must be exactly:

Step 3 — Install the new OBLinux public key

Only if the fingerprint matches:

sudo cp /tmp/oblinux-repo.gpg \
  /usr/share/pacman/keyrings/oblinux-repo.gpg

Step 4 — Update the OBLinux trusted-key definition

echo 'F83C29998D979B913298C40E7E0180391C821D13:4:' | \
  sudo tee /usr/share/pacman/keyrings/oblinux-repo-trusted

Step 5 — Populate Pacman’s OBLinux keyring

sudo pacman-key --populate oblinux-repo

Step 6 — Update normally

sudo pacman -Syu

If oblinux_repo synchronizes without a signing-key error, the migration is complete.