- 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.
