debian-packaging

Automates Debian packaging tasks for git-build workflow, builds, lintian checks, patch management, and reproducible builds.

1|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/UtsavBalar1231/claude-code-configs --skill debian-packaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debian-packaging
Source: https://github.com/UtsavBalar1231/claude-code-configs/tree/main/skills/debian-packaging
Command: npx skills add https://github.com/UtsavBalar1231/claude-code-configs --skill debian-packaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance for Debian packaging, covering git-buildpackage workflows, policy compliance, clean builds, and patch management to ensure reproducible, maintainable packages.

Core Features & Use Cases

  • Git-buildpackage workflows: Manage orig imports, patch queues, and debian branches.
  • Policy compliance: Follow Debian Policy and DEP-3 headers for patches.
  • Clean builds: Use sbuild/pbuilder, chroot testing, and lintian checks.
  • Patch management: Quilt/gbp-pq handling and changelog updates.
  • Upstream integration: Import upstream sources and manage versioning.

Quick Start

Initialize a packaging project with gbp, import upstream sources, and configure debian/ files to begin building.

Frequently Asked Questions about debian-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create reproducible Debian packages using git-buildpackage?

Git-buildpackage automates Debian packaging by managing upstream sources, patch queues, and debian/ directories in a git workflow. Configure gbp.conf, import upstream tarballs, maintain separate debian branches, and use gbp buildpackage to generate .deb packages with consistent, auditable builds.

What are DEP-3 patch headers and why do they matter in Debian packaging?

DEP-3 headers standardize patch metadata in Debian packages by documenting the origin, purpose, and applicability of each patch. They ensure Policy compliance, improve patch maintainability, and enable tools like quilt and gbp-pq to track and apply patches consistently across builds.

How do I use pbuilder and sbuild to validate clean Debian builds?

Pbuilder and sbuild create isolated chroot environments to build .deb packages from source, catching missing dependencies and Policy violations before publication. Combined with lintian quality checks, they verify reproducibility and ensure packages build cleanly on minimal systems.

Can I manage patch queues with quilt in a Debian packaging workflow?

Quilt manages patch stacks by applying, unapplying, and editing patches in sequence within the debian/ directory. Gbp-pq integrates quilt with git-buildpackage, converting patch queues to git branches and back, enabling Policy-compliant patch handling in reproducible builds.

What's the difference between handling upstream sources and maintaining the debian/ directory structure?

Upstream sources are the pristine, unmodified original code imported as tarballs; the debian/ directory contains packaging metadata, patches, and build rules. Git-buildpackage keeps them separate on different branches, ensuring upstream integrity while allowing Debian-specific modifications for Policy compliance.

How does lintian detect packaging violations and improve package quality?

Lintian scans .deb packages and source trees for Debian Policy violations, missing metadata, and common errors. Running lintian as a quality gate catches issues before publication, ensuring packages meet standards for dependencies, permissions, documentation, and reproducibility.