Auto - maintain your Package
summary
Prototype automation called packit uses Git branches and upstream source repositories to auto-generate or consume spec files in upstream, run project tests and distribution tests, and open pull requests that land releases into Fedora rawhide gating once tests pass. It ties existing CI, linters and test wrappers into a gate so new upstream releases automatically build, run tests, and either block or promote changes; early adopters can enable auto-maintenance per-package and inspect produced diffs and logs.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:40Why
- 4:14What if
- 4:58What we need
- 6:21Spec files
- 6:57Inspect generators
- 7:54Test
- 8:46Diagram
- 11:20Gating
- 13:19Pull Requests
- 14:42Benefits
- 15:53What does it mean
- 16:45Challenges
related talks
20mAutomating maintainers work: The Prototype
14mUsing packit and testing farm for CI/CD and automation in an upstream project
48mIntegrating upstream projects downstream
35mPackit: 2 years of upstream ⟷ downstream
45mAutomation for Debian Packaging
13mJourney of Automation - Github, Galaxy, Fedora
50mSustainable package maintenance models
24mManaging Dependencies with Confidence