vyos-build.git/scripts/package-build/libpam-radius-auth/package.toml, branch rollingVyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git)
https://git.amelek.net/vyos/vyos-build.git/atom?h=rolling2026-05-30T17:52:01+00:00T8943: scripts/package-build: migrate broken commit_id refs after 1c rename2026-05-30T17:52:01+00:00Yuriy Andamasovyuriy@vyos.io2026-05-30T17:52:01+00:00urn:sha1:08ef44061c2f8ab211bbabe8c0f27e77033442c1
PR #1204 ("ci: T8943: migrate branch-name refs current->rolling (rollout
1c)") covered .github/workflows/ only and missed seven commit_id values
in scripts/package-build/ that referenced the pre-1c default-branch
names of vyos-owned repos.
The GitHub branch-rename redirect works for the REST API and web UI,
not for git refs in a fresh clone — scripts/package-build/build.py
clones the upstream and `git checkout <commit_id>`, which fails after
the source repo was renamed.
Updated:
libnss-mapuser/package.toml current -> rolling
libpam-radius-auth/package.toml current -> rolling
vpp/package.toml (vyos-vpp-patches) current -> rolling
vyos-1x/package.toml current -> rolling
tacacs/package.toml (libtacplus-map) master -> rolling
tacacs/package.toml (libpam-tacplus) master -> rolling
tacacs/package.toml (libnss-tacplus) master -> rolling
Verified post-rename defaults via `gh api repos/vyos/<r> --jq
.default_branch` for all seven; verified the failure mode via a fresh
`git clone https://github.com/vyos/vyos-1x.git` + `git checkout current`
which errors with "pathspec 'current' did not match any file(s) known
to git".
LTS branches (sagitta/circinus/equuleus) were scanned and require no
changes — only third-party `evgeny-gridasov/openvpn-otp` master appears
there, unaffected by 1c.
🤖 Generated by [robots](https://vyos.io)
T7032: Add missing libpam-radius-auth build2025-01-09T09:05:31+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-09T09:05:31+00:00urn:sha1:528416d4912c513d12443305778f8b56471ef024