- Update debian/changelog: 1.5.1-1~noble1 → 1.5.1-1~trixie1
- Change distribution from noble-backports to trixie
- Add missing build dependencies: libfuse3-dev, libsoup-3.0-dev, etc.
- Update install.sh and README.md to reflect Trixie version
- Fix repository URLs to use particle-os instead of robojerk
- Ensure all required packages are available for successful build
- Add PATH export in debian/rules build step to ensure cargo finds rustup tools
- Fix binary install path to use debian/cargo/target/release/bootc (correct cargo target dir)
- Remove conflicting dh_auto_install call that was looking for wrong binary path
- Add manual package structure creation (usr/share/doc/bootc directory)
- Ensure rustup environment variables are set in workflow step for dpkg-buildpackage
This resolves the 'rustup could not choose a version of cargo' error and
the 'install: cannot stat target/release/bootc' error by properly handling
the CARGO_TARGET_DIR setting and avoiding conflicting install targets.
Build should now complete successfully from cargo compilation through
package creation and upload to Forgejo Debian Package Registry.
- Set rustup environment variables in workflow instead of debian/rules
- Fix binary install path to use debian/cargo/target/release/bootc
- Simplify debian/rules by removing complex rustup handling
- Ensure cargo builds successfully and binary is found during install
