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

Dann führen Sie den folgenden Befehl im Quellverzeichnis des Programms aus:

$ dpkg-buildpackage

Dies wird alles für Sie erledigen, um vollständige Binärpakete und Quellpakete zu erstellen. Im Einzelnen:

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:

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:

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

Dann führt es den folgenden Befehl im Quellverzeichnis aus:

$ dpkg-buildpackage -B

Hiermit wird alles erledigt, um ein architekturabhängiges Binärpaket für eine andere Architektur zu erstellen. Im Einzelnen:

Das ist der Grund, weshalb Sie Ihr Paket auch für andere Architekturen sehen.

Although packages listed in the Build-Depends-Indep field are required to be installed for our normal packaging work (see Abschnitt 6.1, „Kompletter (Neu-)Bau“), 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 Abschnitt 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:

Hiermit können Sie erstellte Pakete mit Ihrem geheimen GPG-Schlüssel im Verzeichnis ~/.gnupg/ unterschreiben.

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

Sie können sich in der erstellten chroot-Umgebung anmelden, indem Sie den Befehl »pbuilder --login --save-after-login« verwenden und diese dann so einrichten wie Sie wollen. Diese Umgebung kann gespeichert werden, indem die Shell-Eingabeaufforderung mittels ^D (Steuerung-D) verlassen wird.

Die aktuelle Version des Programms lintian kann in der chroot-Umgebung ausgeführt werden, indem das Hook-Skript /var/cache/pbuilder/hooks/B90lintian wie folgt eingerichtet wird. ^[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.

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.

These commands use 3 branches to track packaging activity.

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

Wenn Sie mit Ihren Anpassungen fertig sind, vergessen Sie nicht, das Paket gemäß der korrekten Prozedur neu zu bauen. Sie werden .deb-Dateien, die auf diese Weise gebaut wurden, nicht korrekt hochladen können.