Problem: armbian-base-files artifact for jammy fails to build because apt_find_upstream_package_version_and_download_url() looks for 'jammy-updates' in https://github.armbian.com/base-files.json, but only 'jammy' key exists. Root cause: - For Ubuntu LTS (focal, jammy), code sets package_download_release to '${RELEASE}-updates' - JSON file from github.armbian.com only has base release keys (jammy, noble, etc) - jq query returns null for 'jammy-updates' - Artifact excluded from build matrix after 10 retries Solution: Add fallback logic - First try with '-updates' suffix (jammy-updates) - If not found and release ends with '-updates', retry with base release (jammy) - This allows using base release data when -updates is not available Impact: - Fixes jammy base-files artifact build - Allows jammy images to build (they depend on this artifact) - Maintains preference for -updates when available - No impact on other releases (Debian, non-LTS Ubuntu) |
||
|---|---|---|
| .. | ||
| apt-utils.sh | ||
| bat-cat.sh | ||
| chroot-helpers.sh | ||
| cleaning.sh | ||
| countdown.sh | ||
| deprecations.sh | ||
| downloads.sh | ||
| extensions.sh | ||
| git-ref2info.sh | ||
| git.sh | ||
| github-actions.sh | ||
| hash-files.sh | ||
| memoize-cached.sh | ||
| oci-oras.sh | ||
| python-tools.sh | ||
| retry.sh | ||
| shellcheck.sh | ||