feature/rename-backup-diewald-ci #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/rename-backup-diewald-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
- .forgejo/workflows/build.yml with three jobs: * build-deb -> debian:13 container, make deb, uploads .deb + .buildinfo + .changes * build-arch -> archlinux:base-devel container, make arch as builder user, uploads .pkg.tar.zst * release -> on refs/tags/v*, downloads both artifacts and attaches them to the Forgejo release via https://code.forgejo.org/actions/forgejo-release@v2 - Triggers: push main, tag v*, pull_request main, workflow_dispatch. - README: added CI section explaining runner requirements, release publishing behavior and the option to drop the release job on instances without the code.forgejo.org action registry.dh_auto_install invoked the top-level Makefile's `install` target, which is a manual /usr/local convenience installer. That dropped files under /usr/local in the package, so dh_usrlocal aborted the build ("... is not a directory"). Neutralize dh_auto_build/test/install with no-op recipes so the package is assembled solely from debian/install (-> /usr/sbin, /usr/share/doc). The `:` recipe is required: an empty override target would fall through to the `%:` catch-all and mis-invoke dh.