Skip to content

fix(roles/repo_baseos): align Rocky 8 security repo with Rocky 9/10#260

Merged
markuslf merged 2 commits into
mainfrom
feat/repo_baseos-rocky8-security-parity
May 26, 2026
Merged

fix(roles/repo_baseos): align Rocky 8 security repo with Rocky 9/10#260
markuslf merged 2 commits into
mainfrom
feat/repo_baseos-rocky8-security-parity

Conversation

@markuslf
Copy link
Copy Markdown
Member

What

Brings the Rocky 8 Rocky-Security.repo template to parity with the Rocky 9/10 templates (and the upstream stock repo).

Why

The Rocky 8 template only had the [security] stanza and was missing:

  • countme=1 and metadata_expire=6h (the short expiry lets hosts notice emergency hot-fixes within 6h instead of dnf's default cache window),
  • the $rltype mirrorlist variable,
  • the security-debuginfo and security-source sub-repositories (disabled), which Rocky 9/10 and the stock Rocky 8 repo ship.

How

Regenerated the Rocky 8 template from the Rocky 9 one, adjusting only the version path (/rocky/8/) and the gpg key (RPM-GPG-KEY-rockyofficial, which is byte-identical to RPM-GPG-KEY-Rocky-8). The custom-mirror vs. mirrorlist logic, basic-auth handling and enabled toggle are unchanged.

Verification

Rendered both branches (mirror set / unset) and verified against the stock Rocky 8 Rocky-Security.repo. Follow-up to the security repo added in #258's sibling work.

The Rocky 8 `Rocky-Security.repo` only shipped the `[security]` stanza without
`countme`, `metadata_expire=6h` or the `$rltype` mirrorlist variable, and was
missing the `security-debuginfo` / `security-source` sub-repositories that the
Rocky 9/10 templates (and the upstream stock repo) include. Regenerate the Rocky 8
template from the Rocky 9 one (adjusting the version path and the gpg key) so all
Rocky versions are consistent.
@markuslf markuslf requested review from NavidSassan and bhatti-lf and removed request for bhatti-lf May 24, 2026 12:35
@markuslf markuslf merged commit edd4bfd into main May 26, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant