unkinben
134704b3d6
ci/woodpecker/pr/build-fedora44 Pipeline was successful
ci/woodpecker/pr/build-fedora42 Pipeline was successful
ci/woodpecker/pr/build-fedora43 Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/build-almalinux9 Pipeline was successful
ci/woodpecker/pr/build-almalinux8 Pipeline was successful
nzbget is absent from the artifactapi rpm-vendor-el9/rpm-vendor-el8 repodata, so `dnf install nzbget` fails on the media host. Its build.sh requested the download asset using PACKAGE_RELEASE, which carries the dist tag (e.g. 1.el9); upstream only publishes nzbget-<version>-1.x86_64.rpm, so the fetch 404s and a 22-byte junk file gets published that createrepo cannot index. The existing junk nzbget-26.1-1.el9 also makes the deploy dedup probe return 200, blocking re-upload of a corrected 26.1. - Point the build.sh source URL at the upstream release-1 asset name, keeping the dist-tagged local output filename (mirrors code-server). - Bump nzbget el8/el9 to 26.2 (current upstream stable) so the corrected build produces a fresh filename that the deploy step will actually PUT. Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
12 lines
620 B
Bash
Executable File
12 lines
620 B
Bash
Executable File
#!/usr/bin/bash
|
|
|
|
set -e
|
|
|
|
# Download the pre-built RPM from GitHub releases.
|
|
# Upstream always publishes the release-1 asset (nzbget-<version>-1.x86_64.rpm);
|
|
# the source URL must use the upstream asset name, not PACKAGE_RELEASE, which
|
|
# carries the dist tag (e.g. 1.el9) and does not exist upstream. Only the local
|
|
# output filename is dist-tagged, mirroring the code-server package.
|
|
curl -L -o /app/dist/nzbget-${PACKAGE_VERSION}-${PACKAGE_RELEASE}.x86_64.rpm \
|
|
https://artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/github/nzbgetcom/nzbget/releases/download/v$PACKAGE_VERSION/nzbget-${PACKAGE_VERSION}-1.x86_64.rpm
|