Chapter 6. Building the package

Table of Contents

6.1. Complete (re)build
6.2. Autobuilder
6.3. debuild command
6.4. pbuilder package
6.5. git-buildpackage command and similars
6.6. Quick rebuild

We should now be ready to build the package.

In order to perform a complete (re)build of a package properly, you need to make sure you have installed

Then you issue the following command in the source directory:

$ dpkg-buildpackage

This will do everything to make full binary and source packages for you. It will:

  • clean the source tree (debian/rules clean)

  • build the source package (dpkg-source -b)

  • build the program (debian/rules build)

  • build binary packages (fakeroot debian/rules binary)

  • sign the source .dsc file, using gpg

  • create and sign the upload .changes file, using dpkg-genchanges and gpg

The only input that will be required of you is your GPG secret pass phrase, twice. [64] If you are building Debian packages only for your own local use, you can skip promptings for the GPG signatures on the .dsc file and the .changes file like this:

$ dpkg-buildpackage -us -uc

For a non-native Debian package, e.g., gentoo, you will see the following files in the parent directory (~/gentoo) after building packages:

  • gentoo_0.9.12.orig.tar.gz

    This is the original upstream source code tarball, merely renamed to the above so that it adheres to the Debian standard. Note that this was created initially by the dh_make -f ../gentoo-0.9.12.tar.gz.

  • gentoo_0.9.12-1.dsc

    This is a summary of the contents of the source code. The file is generated from your control file, and is used when unpacking the source with dpkg-source(1). This file is GPG signed, so that people can be sure that it's really yours.

  • gentoo_0.9.12-1.debian.tar.gz

    This compressed tarball contains your debian directory contents. Each and every addition you made to the original source code is stored as a quilt patch in debian/patches.

    If someone else wants to re-create your package from scratch, they can easily do so using the above three files. The extraction procedure is trivial: just copy the three files somewhere else and run dpkg-source -x gentoo_0.9.12-1.dsc. [65]

  • gentoo_0.9.12-1_i386.deb

    This is your completed binary package. You can use dpkg to install and remove this just like any other package.

  • gentoo_0.9.12-1_i386.changes

    This file describes all the changes made in the current package revision; it is used by the Debian FTP archive maintenance programs to install the binary and source packages. It is partly generated from the changelog file and the .dsc file. This file is GPG signed, so that people can be sure that it's really yours.

    As you keep working on the package, its behavior will change and new features will be added. People downloading your package can look at this file and quickly see what has changed. Debian archive maintenance programs will also post the contents of this file to the debian-devel-changes@lists.debian.org mailing list.

The long strings of numbers in the .dsc and .changes files are SHA1/SHA256 checksums for the files mentioned. Anyone downloading your files can test them with sha1sum(1) or sha256sum(1) and if the numbers don't match, they'll know the file is corrupt or has been tampered with.

For a native Debian package, e.g., mypackage, you will see the following files in the parent directory after building packages:

  • mypackage_1.0.tar.gz

    This is the source code tarball created from the mypackage-1.0 directory by the dpkg-source command. (Its suffix is not orig.tar.gz.)

  • mypackage_1.0.dsc

    This is a summary of the contents of the source code as in the non-native Debian package. (There is no Debian revision.)

  • mypackage_1.0_i386.deb

    This is your completed binary package as in the non-native Debian package. (There is no Debian revision.)

  • mypackage_1.0_i386.changes

    This file describes all the changes made in the current package version as in the non-native Debian package. (There is no Debian revision.)

Debian supports many ports with the autobuilder network running buildd daemons on computers of many different architectures. Although you do not need to do this yourself, you should be aware of what will happen to your packages. Let's look into roughly how they rebuild your packages for multiple architectures. [66]

For Architecture: any packages, the autobuilder system performs a rebuild. It ensures the installation of

Then it issues the following command in the source directory:

$ dpkg-buildpackage -B

This will do everything to make architecture dependent binary packages on another architecture. It will:

  • clean the source tree (debian/rules clean)

  • build the program (debian/rules build)

  • build architecture dependent binary packages (fakeroot debian/rules binary-arch)

  • sign the source .dsc file, using gpg

  • create and sign the upload .changes file, using dpkg-genchanges and gpg

This is why you see your package for other architectures.

Although packages listed in the Build-Depends-Indep field are required to be installed for our normal packaging work (see Section 6.1, “Complete (re)build”), they are not required to be installed for the autobuilder system since it builds only architecture dependent binary packages. [67] This distinction between normal packaging and autobuilding procedures is what dictates whether you should record such required packages in the Build-Depends or Build-Depends-Indep fields of the debian/control file (see Section 4.1, “control).

You can automate the dpkg-buildpackage command's package build process further with the debuild command. See debuild(1).

Customization of the debuild command can be done through /etc/devscripts.conf or ~/.devscripts. I would suggest at least the following items:

DEBSIGN_KEYID=Your_GPG_keyID
DEBUILD_LINTIAN_OPTS="-i -I --show-overrides"

With these, packages are signed by your specified GPG key ID (good for sponsoring packages) and checked in detail by the lintian command.

Cleaning the source and rebuilding the package from your user account is as simple as:

$ debuild

Here, if you are building Debian packages only for your own local use, you can skip promptings for the GPG signatures on the .dsc file and the .changes file like this:

$ debuild -us -uc

You can clean the source tree as simply as:

$ debuild clean

For a clean room (chroot) build environment to verify the build dependencies, the pbuilder package is very useful. [68] This ensures a clean build from the source under the sid auto-builder for different architectures and avoids a severity serious FTBFS (Fails To Build From Source) bug which is always in the RC (release critical) category. [69]

Let's customize the pbuilder package as follows:

  • setting the /var/cache/pbuilder/result directory writable by your user account.

  • creating a directory, e.g. /var/cache/pbuilder/hooks, writable by the user, to place hook scripts in.

  • configuring ~/.pbuilderrc or /etc/pbuilderrc to include the following.

    AUTO_DEBSIGN=${AUTO_DEBSIGN:-yes}
    HOOKDIR=/var/cache/pbuilder/hooks
    

This will allow you to sign generated packages with your secret GPG key in the ~/.gnupg/ directory.

First let's initialize the local pbuilder chroot system as follows.

$ sudo pbuilder create

If you already have a completed source package, issue the following commands in the directory where the foo.orig.tar.gz, foo.debian.tar.gz, and foo.dsc files exist to update the local pbuilder chroot system and to build binary packages in it.

$ sudo pbuilder --update
$ sudo pbuilder --build foo_version.dsc

The newly built packages without the GPG signatures will be located in /var/cache/pbuilder/result/ with non-root ownership.

The GPG signatures on the .dsc file and the .changes file can be generated as:

$ cd /var/cache/pbuilder/result/
$ debsign foo_version.dsc
$ debsign foo_version_arch.changes

If you have an updated source tree but have not generated the matching source package, issue the following commands in the source directory where the debian directory exists, instead.

$ sudo pbuilder --update
$ pdebuild

Here, if you are building Debian packages only for your local use, you can skip promptings for the GPG signatures on the .dsc file and the .changes file as:

$ AUTO_DEBSIGN=no pdebuild

You can log into its chroot environment with the pbuilder --login --save-after-login command and configure it as you wish. This environment can be saved by leaving its shell prompt with ^D (Control-D).

The latest version of the lintian command can be executed in the chroot environment using the hook script /var/cache/pbuilder/hooks/B90lintian configured as follows. [70]

#!/bin/sh
set -e
install_packages() {
        apt-get -y --force-yes install "$@"
        }
install_packages lintian
echo "+++ lintian output +++"
su -c "lintian -i -I --show-overrides /tmp/buildd/*.changes" - pbuilder
# use this version if you don't want lintian to fail the build
#su -c "lintian -i -I --show-overrides /tmp/buildd/*.changes; :" - pbuilder
echo "+++ end of lintian output +++"

You need to have access to the latest sid environment to build packages properly for sid. In practice, sid may be experiencing issues which makes it undesirable for you to migrate your whole system. The pbuilder package can help you to cope with this kind of situation.

You may need to update your stable packages after their release for stable-proposed-updates, stable/updates, etc. [71] For such occasions, the fact you may be running a sid system is not a good enough excuse for failing to update them promptly. The pbuilder package can help you to access environments of almost any Debian derivative distribution of the same architecture.

See http://www.netfort.gr.jp/~dancer/software/pbuilder.html, pdebuild(1), pbuilderrc(5), and pbuilder(8).

If your upstream uses a source code management system (VCS) [72] to maintain their code, you should consider using it as well. This makes merging and cherry-picking upstream patches much easier. There are several specialized wrapper script packages for Debian package building for each VCS.

  • git-buildpackage: a suite to help with Debian packages in Git repositories.

  • svn-buildpackage: helper programs to maintain Debian packages with Subversion.

  • cvs-buildpackage: a set of Debian package scripts for CVS source trees.

Use of git-buildpackage is becoming quite popular for Debian Developers to manage Debian packages with the Git server on alioth.debian.org. [73] This package offers many commands to automate packaging activities.

  • git-import-dsc(1): import previous Debian package to a Git repository.

  • git-import-orig(1): import new upstream tar to a Git repository.

  • git-dch(1): generate the Debian changelog from Git commit messages.

  • git-buildpackage(1): build Debian packages from a Git repository.

  • git-pbuilder(1): build Debian packages from a Git repository using pbuilder/cowbuilder.

These commands use 3 branches to track packaging activity.

  • main for Debian package source tree.

  • upstream for upstream source tree.

  • pristine-tar for upstream tarball generated by the --pristine-tar option.[74]

You can configure git-buildpackage with ~/.gbp.conf. See gbp.conf(5). [75]

With a large package, you may not want to rebuild from scratch every time while you're tuning details in debian/rules. For testing purposes, you can make a .deb file without rebuilding the upstream sources like this[76]:

$ fakeroot debian/rules binary

Or simply do the following to see if it builds or not:

$ fakeroot debian/rules build

Once you are finished with your tuning, remember to rebuild following the proper procedure. You may not be able to upload correctly if you try to upload .deb files built this way.



[64] This GPG key must be signed by a Debian developer to get connected to the web of trust and must be registered to the Debian keyring. This enables your uploaded packages to be accepted to the Debian archives. See Creating a new GPG key and Debian Wiki on Keysigning.

[65] You can avoid applying quilt patches in the 3.0 (quilt) source format at the end of the extraction with the --skip-patches option. Alternatively, you can run dquilt pop -a after normal operation.

[66] The actual autobuilder system involves much more complicated schemes than the one documented here. Such details are beyond the scope of this document.

[67] Unlike under the pbuilder package, the chroot environment under the sbuild package used by the autobuilder system does not enforce the use of a minimal system and may have many leftover packages installed.

[68] Since the pbuilder package is still evolving, you should check the actual configuration situation by consulting the latest official documentation.

[69] See http://buildd.debian.org/ for more on Debian package auto-building.

[70] This assumes HOOKDIR=/var/cache/pbuilder/hooks. You can find many examples of hook scripts in the /usr/share/doc/pbuilder/examples directory.

[71] There are some restrictions for such updates of your stable package.

[73] Debian wiki Alioth documents how to use the alioth.debian.org service.

[74] The --pristine-tar option invokes the pristine-tar command which can regenerate an exact copy of a pristine upstream tarball using only a small binary delta file and the contents of the tarball, which are typically kept in an upstream branch in the VCS.

[75] Here are some web resources available for advanced audiences.

[76] Environment variables which are normally configured to proper values are not set by this method. Never create real packages to be uploaded using this quick method.