Tricks to convince alma that my fedora 43 repo is alma 9
Some checks failed
CI / test (push) Successful in 47s
CI / test (almalinux, docker.io/library/almalinux:9, python3.11) (push) Failing after 11m32s
CI / test (debian, docker.io/library/debian:13, python3) (push) Successful in 19m21s
Lint / test (push) Successful in 46s

This commit is contained in:
Miguel Jacq 2026-06-21 17:02:01 +10:00
parent ddd118e3bb
commit c541fd1d6b
Signed by: mig5
GPG key ID: 03906B4110AAD3B8

View file

@ -268,27 +268,50 @@ ensure_puppet_repo() {
DNF_UPDATED=
}
mig5_rpm_releasever() {
if [[ -n "${ENROLL_TEST_MIG5_RPM_RELEASEVER:-}" ]]; then
printf '%s' "${ENROLL_TEST_MIG5_RPM_RELEASEVER}"
return
fi
if [[ "$(os_id)" == "fedora" ]]; then
os_version_major
return
fi
# mig5 currently publishes Fedora RPM repositories only. For RPM-family
# CI hosts such as AlmaLinux, use a Fedora repository explicitly instead of
# letting dnf expand $releasever to Alma's major version, e.g. 9.
printf '43'
}
ensure_mig5_rpm_repo() {
if ! is_rpm_family; then
return
fi
if [[ -e /etc/yum.repos.d/mig5.repo ]]; then
local repo_file
local releasever
repo_file=/etc/yum.repos.d/mig5.repo
releasever="$(mig5_rpm_releasever)"
if [[ -e "${repo_file}" ]] && grep -Fq "baseurl=https://rpm.mig5.net/${releasever}/rpm/" "${repo_file}"; then
return
fi
section "Setup: mig5 dnf repository"
pkg_install ca-certificates curl
run rpm --import https://mig5.net/static/mig5.asc
cat >/etc/yum.repos.d/mig5.repo <<'EOF'
cat >"${repo_file}" <<EOF
[mig5]
name=mig5 Repository
baseurl=https://rpm.mig5.net/$releasever/rpm/$basearch
name=mig5 Repository (Fedora ${releasever} packages)
baseurl=https://rpm.mig5.net/${releasever}/rpm/\$basearch
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mig5.net/static/mig5.asc
EOF
run dnf -y upgrade --refresh
DNF_UPDATED=1
DNF_UPDATED=
}
ensure_jinjaturtle() {