This issue tracker is dedicated to managing the automated Arch Linux package build pipeline. Please review the following guidelines before submitting a new issue to ensure prompt and efficient resolution.
- Search existing issues: Verify that your issue or request has not already been reported.
- Verify upstream status: If a package fails to build, check the Arch User Repository (AUR) page for that specific package. Build failures are frequently caused by upstream source changes or broken
PKGBUILDfiles, which must be fixed by the AUR maintainer.
1. Build Failures If a package currently in the automated rotation fails its daily build, please provide:
- The exact name of the failing package.
- The date of the failed build run.
- Relevant excerpts from the CI build logs showing the error.
2. Package Requests To request a new AUR package be added to the daily automated build schedule, please provide:
- The exact package name as it appears on the AUR.
- A brief explanation of why it requires daily automated rebuilds (e.g.,
-gitpackage, frequent upstream updates).
3. CI Pipeline Bugs For technical issues regarding the Docker environment, build scripts, or automation configuration:
- Describe the expected behavior versus the actual behavior.
- Provide steps to reproduce the issue locally, if applicable.
Issues determined to be the result of broken upstream source code or invalid AUR PKGBUILD configurations will be documented and closed, as these require intervention from the respective AUR package maintainers rather than modifications to this CI pipeline.