openKylin core developer Zhang Pangave a presentation titled《From Build Failures to Reviewable Patches: Salsa CI Auto-Fix Practices》a technical sharing, focusing on the processing of batch build failure tasks, introducing the design concept of an automated repair scheduler, and exploring the application of related methods in Debian package maintenance scenarios.

This sharingoriginates from the openKylin community's continuous practice in automatic package repair. During distribution maintenance, a build-failed package often needs to go through multiple steps such as log capture, root cause analysis, code modification, patch organization, packaging and uploading, and result tracking. Facing hundreds of pending tasks, repetitive operations, progress tracking, and recovery after interruptions all increase maintenance costs. To address these issues,the openKylin community technical team developed an automatic repair scheduling tool autofix-dispatcher, through the collaboration of multiple AI agents, organizing the above steps into a sustainable batch repair process.

According to the team's project statistics, the autofix-dispatcher has cumulatively and automatically fixed over 2000 build-failed source packages in the openKylin build environment, with a repair success rate of 99%.The tool can automatically connect log analysis, code repair, patch solidification, package upload, build result query, and status backfill, supporting unattended batch task operation and reducing developers' manual per-package handling.The repetitive work of processing and continuously monitoring build results.

• Architecture division of labor: Main agent dispatches tasks, repair sub-agent performs analysis and fixes, status query sub-agent tracks build results; a unified task ledger records the status flow of each package (pending fix → fixing → uploaded → build success/stopped) and reasons.

• Three-round model relay: First round: lightweight model quick attempt, if failed escalate to model + chroot build verification, third round switch to another model to continue; stop recording if exceeded, no invalid retries. Supporting skills: log root cause analysis, version number/changelog management, quilt patch solidification, source package upload, etc. Problem experience is accumulated into the memory bank.

• Long-term operation guarantee: Multi-instance concurrent repair, file lock protects ledger read/write, task lease + heartbeat prevents duplicate claims; after an instance interruption, other instances take over tasks through recovery scanning after lease expiration.

• Build constraintsTasks judged to have insufficient software sources/dependencies shall stop modifications and record the reason; use a fixed chroot environment for build verification to exclude local differences; upload results and backfill records based on the actual feedback from the build service.

By participating in MiniDebConf Beijing 2026, openKylin shared with the open-source community its practical achievements in automatic package repair, providing a reference for more developers to improve maintenance workflows and enhance collaboration efficiency.

Going forward,openKylin will continue its technical exploration centering on package maintenance and build automation, refine development tools and collaboration processes, strengthen experience exchanges with the open-source community, promote the application of automation capabilities in more maintenance scenarios, and jointly improve the Linux software ecosystem.。

The openKylin Packaging SIG is primarily responsible for maintaining community package packaging specifications and public packages, coordinating package dependency issues during the community release process, and providing support for package maintenance and version releases. Developers interested in Linux package packaging, maintenance, and automation tool development are welcome to participate in exchanges and co-construction.

SIG homepage:

https://gitee.com/openkylin/community/tree/master/sig/packaging