- 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
- Remove unnecessary Rust compilation steps (not needed for Debian packaging)
- Change container from rust:trixie to debian:trixie
- Streamline workflow to go directly to Debian package build
- Keep dh-cargo for proper Debian packaging
- Fix workflow to match bootc-deb repository structure
- Replace multiple workflow files with single consolidated ci.yml
- Fix container image from debian:latest to debian:trixie
- Add apt-cacher-ng support for faster builds
- Include comprehensive CI pipeline: build, security, validation
- Add proper secrets handling with ACCESS_TOKEN
- Target Debian Trixie distribution
- Remove old Ubuntu Noble references
- Improve build reliability and artifact collection
- Change container from ubuntu:latest to debian:latest
- Update distribution target from noble to trixie
- Fix package version from 1~noble1 to 1~trixie1
- Update environment variable from UBUNTU_VERSION to DEBIAN_VERSION
- Remove hardcoded libostree dependency versions
- Update upload URLs to use trixie/main
- Fix build summary to show Debian version
- Ensure compatibility with Debian Trixie systems
- Add rustup environment variables (PATH, CARGO_HOME, RUSTUP_HOME) to test workflow
- Add 'rustup default stable' call to ensure default toolchain is set
- Match the exact environment setup that works in the main workflow
- Update todo.md to reflect the latest fix and completed main goal
This ensures the test workflow has the same rustup environment as the main workflow
and should now pass both cargo build and dpkg-buildpackage steps without rustup errors.
- Add Forgejo repository setup to test workflow for libostree packages
- Install libostree-dev and libostree-1-1 from Forgejo registry
- Add all missing Debian build dependencies: debhelper-compat, dh-cargo, cargo, rustc
- Add system library dependencies: libcurl4-gnutls-dev, libfuse3-dev, libsoup-3.0-dev
- Add documentation dependencies: gobject-introspection, gtk-doc-tools, docbook-xml, etc.
- Update todo.md to reflect completed main goal and next steps
This ensures the test workflow has all the same dependencies as the main workflow
and should now pass both cargo build and dpkg-buildpackage steps.
- 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
- Add rustup default stable in build step for proper toolchain setup
- Install libzstd-dev for zstd-sys crate compatibility
- Fix rustup toolchain context issues in main workflow
- Add missing zstd development libraries to both workflows
- Ensure all Rust crate dependencies are available
- Use bash shell and POSIX-compliant sourcing
- Add debhelper-compat, dh-cargo, rustc, cargo packages
- Install system Rust before rustup for dpkg compatibility
- Updated workflow to use ACCESS_TOKEN instead of FORGEJO_TOKEN
- Added comprehensive setup instructions in workflow comments
- Updated all API calls and debug steps to use ACCESS_TOKEN
- Added reminder for future repository setups
- Add automatic README update workflow that triggers after successful builds
- Add manual workflow for updating download links to specific builds
- Update README with working download links to Build 97 artifacts
- Include direct links to both main package and debug symbols
- Add installation instructions with correct workflow run URLs
- Fix workflow run ID references and artifact download paths
This provides reliable download links that users can access directly
from the repository README to install the latest libostree backport.
- Replace system Rust 1.75.0 with rustup to get latest stable Rust
- Update both build-packages.yml and test-build.yml workflows
- Add source ~/.cargo/env to all Rust build steps
- Add Rust version verification in setup steps
This resolves the "requires rustc 1.82.0 or newer" error that was
preventing bootc from building in the CI/CD environment.
- Update patch file to use correct path: lib/src/cli.rs instead of crates/lib/src/cli.rs
- Simplify patch application to use patch -p1 with correct strip level
- Fix debug step to check correct directory structure
- Add -y flag to all apt update commands to prevent interactive prompts
- Ensure all apt commands use non-interactive mode with proper environment variables
This resolves the "can't find file to patch" error and prevents
interactive prompts that were causing CI/CD failures.
- Add debugging step to show file structure before patching
- Add logic to try different patch strip levels (-p1 vs -p0)
- Add error handling to show available Rust files if target not found
- Add artifact upload steps for both libostree and bootc packages
- Create release-assets directory with build summary
- Copy all .deb packages to artifacts directory for visibility
This fixes the "can't find file to patch" error and ensures
built packages are accessible as artifacts in the CI/CD workspace.
- Add DEBIAN_FRONTEND=noninteractive to prevent apt prompts
- Add APT_LISTCHANGES_FRONTEND=none to disable package change notifications
- Change from apt to apt-get for better CI/CD compatibility
- Add apt-get update before installing build dependencies
- Add --no-install-recommends flag to reduce package count
This fixes the "Do you want to continue? [Y/n]" prompt that was
causing the libostree backport build to fail in the CI environment.
