- Use ACCESS_TOKEN instead of FORGEJO_USERNAME/FORGEJO_TOKEN
- Use --upload-file without -X PUT (automatic PUT method)
- Add proper HTTP status code handling and response parsing
- Match exact pattern from working composefs CI
- This should resolve the reqPackageAccess issue
- Use PUT method for Forgejo uploads as per documentation
- Fix dch backport by using --force-distribution and EDITOR=true
- This should resolve both the reqPackageAccess and dch editor issues
- Upload should now work properly with correct HTTP method
- Use correct API endpoint: /api/packages/particle-os/debian/pool/trixie/main/upload
- Match the format used in the working composefs CI
- This should resolve the 404 page not found errors
- Build is working perfectly, just need correct upload URL
- Change from GET with query params to POST with proper authentication
- Use --user instead of Authorization header for better compatibility
- This should resolve the 404 page not found errors during upload
- Build was successful, just need to fix the upload step
- Replace manual package installation with 'apt build-dep -y .'
- Use 'debuild -b -us -uc' instead of dpkg-buildpackage
- Follow standard Debian package building workflow
- Much simpler and more reliable than manual dependency management
- This is the proper way to build Debian packages
- Replace libzlib-dev with zlib1g-dev (correct Debian package name)
- Remove libxz-dev (doesn't exist, use liblzma-dev instead)
- Remove duplicate packages that were listed twice
- This should resolve the 'Unable to locate package' errors
- Replace mk-build-deps and apt-get build-dep with specific package list
- Avoid installing full GNOME desktop and GUI packages
- Install only essential build dependencies for ostree
- Fix dch editor issues by setting environment variables and using echo y
- This should resolve the build failures and avoid unnecessary packages
- Move setup step before checkout step
- Install git and essential tools before trying to use git
- This should resolve the 'git: not found' error
- Proper order: setup environment -> checkout code -> build packages
- Add git to the essential tools installation step
- Debian:unstable container is minimal and doesn't include git by default
- Install git, curl, build-essential, fakeroot, devscripts in setup step
- This should resolve the 'git: not found' error in the checkout step
- Switch to debian:unstable container to avoid Ubuntu/Debian mixing issues
- Remove sudo commands since we're running as root in container
- This should resolve the GPG key verification problems
- Proper Debian environment for building Debian packages
- Much cleaner approach than trying to add Debian repos to Ubuntu
- Restore apt-cacher-ng detection and configuration like composefs CI
- Use proxy sources when apt-cacher-ng is available (192.168.1.101:3142)
- Fallback to standard Debian mirrors when apt-cacher-ng is not available
- This should resolve the GPG key verification issues
- Follows the same pattern as the working composefs CI
- Remove Docker-in-Docker complexity that was causing build script issues
- Use direct approach on Ubuntu runner with Debian repositories
- Follow the same pattern as the working composefs CI
- Much simpler and more reliable - no container networking issues
- Just add Debian repos to Ubuntu runner and build directly
- Remove container from job definition to avoid network issues
- Use Docker-in-Docker approach with proper Debian unstable environment
- Create build script that runs inside Docker container
- This should resolve the 'forgejo hostname not found' issue
- Simpler and more reliable than trying to mix Ubuntu runner with Debian packages
- Use docker.io/node:iron-trixie instead of debian:unstable
- This provides Node.js support for GitHub Actions while using Debian Trixie base
- Should resolve the 'node: executable file not found' error
- Better compatibility with actions/checkout@v4 and other Node.js-based actions
- Remove custom Dockerfile as it's redundant with Forgejo runner containerization
- Use debian:unstable-slim container directly like apt-ostree CI
- Run all build steps directly on the runner for better visibility
- Follow Debian SimpleBackportCreation guidelines for proper backporting
- This should provide much better logging and debugging visibility
- Based on apt-ostree CI workflow as reference
- Add dch --bpo to add backport revision number as per Debian guidelines
- Add fakeroot debian/rules binary test build before main build
- Use dpkg-buildpackage --build=binary --unsigned-changes as recommended
- This follows the SimpleBackportCreation workflow from Debian wiki
- Should finally produce proper .deb binary packages
- The .sources format was not being recognized by apt source command
- apt source ostree requires traditional sources.list format with deb-src lines
- This fixes the root cause of the build failure where apt source was failing silently
- Now both apt-cacher-ng and standard mirrors use sources.list format
- Changed 'docker cp CONTAINER_ID:/workspace/ .' to 'docker cp CONTAINER_ID:/workspace/. .'
- The trailing '.' copies the contents of /workspace/ directly to current directory
- This prevents creating a workspace/ subdirectory that breaks the upload step
- Should fix the issue where .deb files were in wrong location
- The CI was overriding the Dockerfile's fixed sources configuration
- This was causing apt source ostree to fail silently
- Now both apt-cacher-ng and standard mirrors use .sources format
- This should finally allow the build to proceed to dpkg-buildpackage
- Add debugging output to see what happens during apt source ostree
- Add error handling to catch if apt source fails
- This will help identify where the build is actually failing
- Use --build=source,binary instead of --build=any,all for dpkg-buildpackage
- Add apt-get build-dep -y . to install build dependencies properly
- This follows Debian best practices for building binary packages
- Add --build=any,all flag to dpkg-buildpackage to force binary package creation
- Install additional build tools (build-essential, fakeroot, devscripts)
- This should ensure .deb files are actually created instead of just source packages
- Add verbose output to dpkg-buildpackage command
- Show debian/rules and debian/changelog contents
- Add more detailed error checking for build failures
- This will help identify why only source packages are being created
- Replace problematic grep -E with multiple simple grep commands
- This avoids shell interpretation issues with the pipe character in the pattern
- Each dependency is checked individually for better debugging
