Automation for Debian Packaging
summary
A web scheduler called Debian Janitor runs automated fixes across Git repositories using lintian-brush scripts and the silver-platter runner, creating or pushing merge requests after build and autopkgtest verification. About 10,000 changes are pushed directly and ~7,000 merge requests merged; automated upstream imports succeed for ≈20% (≈2,200 releases) while ~35% are already current. The system rate-limits per maintainer, discards changes when builds or tests fail, and still faces missing VCS metadata and ≈52% of merged repo changes not yet uploaded to the archive.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:16Automation For Debian Packaging
- 1:44Linux Distributions
- 3:41The Debian Distribution
- 6:19Ecosystem Improvements
- 9:03debian/upstream/metadata
- 10:43autopkgtest
- 11:32debhelper adoption
- 14:35Making large-scale Changes
- 18:16Lintian-Brush: Example Fixer
- 19:22Adoption Challenges
- 22:40Scaling Up
- 23:31Debian Janitor
- 24:20Philosophy
- 24:34Core Principles
- 28:53Ongoing Maintenance
- 30:44Impact So Far
- 32:40Supported Hosting Sites
- 38:13Importing New Upstreams Across The Archive
- 40:36Users: Installing Packages
- 41:05What's Next?
- 41:23Future Plans
- 41:54Debian - Harder Problems
- 42:06Beyond Debian
- 43:20Standing on the Shoulders of Giants
related talks
24mAuto - maintain your Package
45mFinding problems quickly in a quickly evolving opensource project
39mManaging an Open Source Project
17mBuilding Secure Open Source Communities From the Ground Up
20mAutomating maintainers work: The Prototype
14mUsing packit and testing farm for CI/CD and automation in an upstream project
56mMaintainer_s Diary - We Have a Scaling Problem
42mThe Long Road to Reproducible Builds