Private
Public Access
1
0
Files
linux_patch_api/debian/control
Draco Lunaris 32803ff27c
Some checks failed
CI/CD Pipeline / Code Format (push) Successful in 2s
CI/CD Pipeline / Clippy Lints (push) Successful in 46s
CI/CD Pipeline / All Unit Tests (push) Successful in 1m11s
CI/CD Pipeline / Security Audit (push) Successful in 5s
CI/CD Pipeline / Enrollment Tests (push) Successful in 1m27s
CI/CD Pipeline / Build Debian Package (Ubuntu 22.04) (push) Failing after 5s
CI/CD Pipeline / Verify Enrollment CLI Flag (push) Successful in 1m5s
CI/CD Pipeline / Build Debian Package (push) Failing after 4s
CI/CD Pipeline / Build Arch Package (push) Successful in 2m22s
CI/CD Pipeline / Build RPM Package (push) Successful in 2m17s
CI/CD Pipeline / Build Alpine Package (push) Successful in 3m7s
fix: switch to build-package.sh for .deb builds
* fix: switch to build-package.sh for .deb builds

Replace dpkg-buildpackage with scripts/build-package.sh using
dpkg-deb --build approach. This bypasses the dpkg-buildpackage
subprocess chain (dh → make → debian/rules → cargo) which
does not inherit the rustup environment (RUSTUP_HOME, CARGO_HOME,
default toolchain) from GitHub Actions.

Same approach as Linux-Patch-Manager which passes CI.

- Add scripts/build-package.sh (modeled after Manager)
- Add Version and Installed-Size to debian/control
- Update CI workflow to use build-package.sh
- Fix release files path (project root, not ../)

* fix: extract only binary package paragraph from debian/control

dpkg-deb --build expects a single control paragraph starting
with Package: field. The debian/control file has two paragraphs
(source + binary). The awk command extracts only the binary
package paragraph to avoid dpkg-deb parse errors.

* fix: generate DEBIAN/control from scratch in build-package.sh

dpkg-deb --build is fundamentally incompatible with debian/control
which uses dpkg-buildpackage substitution variables like
${shlibs:Depends} and ${misc:Depends}. Generate a clean control
file from scratch in the script to eliminate all incompatibilities.

- No substitution variables
- No source paragraph
- No Build-Depends
- Homepage points to GitHub
- Installed-Size calculated before control file generation

---------

Co-authored-by: git-echo <git-echo@moon-dragon.us>
2026-05-31 11:19:47 -05:00

37 lines
1.1 KiB
Plaintext

Source: linux-patch-api
Section: admin
Priority: optional
Maintainer: Echo <echo@moon-dragon.us>
Build-Depends: debhelper (>= 12),
cargo,
rustc,
libsystemd-dev,
pkg-config
Standards-Version: 4.6.0
Homepage: https://gitea.moon-dragon.us/echo/linux_patch_api
Vcs-Git: https://gitea.moon-dragon.us/echo/linux_patch_api.git
Vcs-Browser: https://gitea.moon-dragon.us/echo/linux_patch_api
Package: linux-patch-api
Architecture: amd64
Version: 1.2.0-1
Installed-Size: 0
Depends: systemd,
libsystemd0,
${shlibs:Depends},
${misc:Depends}
Description: Secure remote package management API for Linux systems
Linux Patch API provides a secure, mTLS-authenticated REST API for
remote package management operations including:
- Package installation and removal
- Security patch application
- System health monitoring
- Job queue management with WebSocket status streaming
.
Features:
- Mutual TLS (mTLS) authentication
- IP whitelist enforcement
- Asynchronous job processing
- Comprehensive audit logging
- Systemd integration with security hardening