Fedora package update? Assess its impact in Copr
summary
Procedure uses repoquery, PKG_NAME, the copr CLI and parallel to create an isolated Copr repo, build an updated RPM and then rebuild all dependents. Example modifies python-rich with Emoji module removed and finds 32 build-time dependents. Copr build runs, copr monitor reports 4 failures then control rebuild leaves 1 failing package. Workflow surfaces which packages actually break, provides failing buildlogs to inspect, and results in opening tickets or coordinating fixes before landing the update.
AI-written summary · about
chapters (14)
- 0:00Package updates in Fedora
- 2:11Impact checks before updates
- 5:01Copr for impact testing
- 8:15Querying Fedora repos
- 13:47Copr impact check process
- 16:38Adding packages in Copr
- 18:52Automating rebuilds with webhooks
- 21:42Evaluating build results
- 24:58Review and next steps
- 27:09Failed builds and communication
- 29:19Copr version constraints
- 31:28Resources and reading
- 32:17Log analysis for failed builds
- 35:19Q&A
related talks
50mDo our development tools need a refresh?
23mFlatpaks in Fedora - an update
24mAuto - maintain your Package
26mPackager Dashboard - Life of packager made easy
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
30mControl all of your projects with copier!
16mManaging multiple packages in a monorepo
34mSolving Poly-Repo Dependency Nightmares