Follow-up fixes from adversarial verification of the Gitea adaptation:
- build.yml: arm64 `bindeb-pkg` cross build aborted on the linux-headers
package because CONFIG_MODULE_SIG_FORMAT=y makes it cross-compile
scripts/sign-file, which needs arm64 OpenSSL dev headers that aren't
installed. Pass DEB_BUILD_PROFILES=pkg.linux-upstream.nokernelheaders on
the arm64 make line (the maintainers' documented remedy) so the arm64
release publishes an image package without the unbuildable headers deb.
- install.sh: api_get used `curl -fsSL`, which discards the HTTP error body,
so Gitea's {"message":...} never reached check_release_api_response and the
token/permission hint was dead on 401/403/404. Drop -f (keep -sSL) so the
error JSON is surfaced; network-layer failures still exit non-zero.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Retarget the build pipeline and installer from GitHub to the
git.chilldove.com Gitea instance (icePigeon/linux-kernel-bbrv3).
- build.yml: replace gh CLI release checks and softprops/action-gh-release
with Gitea REST API calls (curl); drop the GitHub-only delete-workflow-runs
cleanup job; authenticate via the auto-injected GITEA_TOKEN.
- Avoid actions/upload-artifact@v4 / download-artifact@v4 (they abort on
Gitea as GHES): pass the config baseline between jobs via Gitea release
assets instead of artifacts, and drop the redundant deb/marker artifacts.
- Cross-compile arm64 on the single x86_64 runner
(CROSS_COMPILE=aarch64-linux-gnu-, gcc-aarch64-linux-gnu); thread
CROSS_COMPILE through prepare-kernel-config.sh olddefconfig.
- install.sh: fetch releases from the Gitea API, self-update and CVE
detector from Gitea raw URLs, token-authenticated asset downloads,
paginate the release list; keep GITHUB_TOKEN/GH_TOKEN as fallbacks.
- README.md: point install/download URLs at Gitea, reword GitHub -> Gitea,
remove the GitHub-only Star History widget.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rename the kernel LOCALVERSION used by the build from
-joeyblog-bbrv3 / -joeyblog-bbrv3-max to -bbrv3 / -bbrv3-max, so the
produced uname strings and .deb package names no longer carry the
custom brand. Standard vs max kernels stay distinguishable.
- .github/workflows/build.yml: matrix localversion for all four jobs
- scripts/build-bbrv3-max-kernel.sh: LOCALVERSION for local max builds
- install.sh: update detection, profile matching, expected-uname and
uninstall logic to key off -bbrv3 / -bbrv3-max instead of joeyblog
- README.md: describe uninstall by the new package-name suffixes
Runtime config paths (e.g. /etc/sysctl.d/99-joeyblog.conf) and author
attribution are unchanged; they are not kernel names.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PvXBX9hm6GzStHUMDZzDoZ
Claude