Diff for "PbuilderHowto"

PbuilderHowto

Differences between revisions 22 and 23

Introduction

This document describes the steps to setup a chroot jail for building Ubuntu packages using pbuilder. It is recommended for Ubuntu maintainers or anyone interested in building packages using Ubuntu.

You can build packages without pbuilder but you must already have all the build dependencies of the package that you are building installed on your running system.

The following assume you want to install breezy. If you need a hoary or dapper chroot, then exchange breezy with the appropriate distribtion.

Installing Pbuilder on dapper

The latest pbuilder package in dapper (0.145ubuntu3) should work out of the box. You only need to install it and debootstrap. Then run:

sudo pbuilder create

and then

sudo pbuilder build my-package_1.0.dsc

Installing Pbuilder on warty, hoary, breezy

Install pbuilder package and debootstrap.

Edit /etc/pbuilder/pbuilderrc changing the following directives:

    MIRRORSITE=http://archive.ubuntu.com/ubuntu
    DISTRIBUTION=breezy

Since pbuilder will complain about unauthenticated packages, you have to allow unauthenticated packages. You can make it like so:

Edit your /etc/pbuilder/pbuilderrc:

    APTCONFDIR="/etc/pbuilder/apt.config/"

Now you'll copy needed files of /etc/apt to it and

    sudo -s
    mkdir /etc/pbuilder/apt.config/
    cp -ar /etc/apt/* /etc/pbuilder/apt.config/
    echo "APT::Get::AllowUnauthenticated 1;" >> /etc/pbuilder/apt.config/apt.conf.d/allow-unauthenticated
    exit

NOTE: Make sure to remove 99update-notifier from /etc/pbuilder/apt.config/apt.conf.d/ if you have copied it in the last step. It can potentially break future updates to your pbuilder chroot, as update-notifier won't normally be installed.

Save the file and run the command below to build your breezy chroot:

    sudo pbuilder create --distribution breezy

Rebuilding a package

If you reach this point you now have a Breezy chroot located at /var/cache/pbuilder ready to build a package. We will get a Debian source package from Ubuntu repository to test it.

To check if you can download source packages, you will need an uncommented deb-src line in /etc/apt/sources.list, containing:

    deb-src http://archive.ubuntu.com/ubuntu breezy main restricted

If the line above is there but not uncommented, uncomment it. Make sure your package index files are synchronized so that apt-get knows where to find the sources:

    sudo apt-get update

We will build bc, a simple calculator, from source, let's download the debian source package from ubuntu repository:

    sudo apt-get source bc

You can build the package using your Breezy chroot with the command:

    sudo pbuilder build *.dsc

In the end, the binary and source package will be at /var/cache/pbuilder/result/

Updating a chroot

I recommend you update your chroot before each build, to this task use the comand below:

    sudo pbuilder update

Universe support

If you want to rebuild a package from universe or build a new one that needs a package out of main you will need to edit /etc/pbuilderrc again, changing:

    OTHERMIRROR="deb http://archive.ubuntu.com/ubuntu breezy universe multiverse"

Now you need to update your chroot with the new configuration:

    sudo pbuilder update --distribution breezy --override-config

Upgrading to Latest Development Release

If you want to participate in the current release cycle, you will want to have a DapperDrake chroot. Sometimes, the development version may not be installable directly. In this case, you have to install the latest release first, and upgrade then to development release

change all occurences of breezy in /etc/pbuilderrc and /etc/pbuilder/apt.config/ to dapper
sudo pbuilder update --override-config
use the --override-config option every time you run the update

Note: If you are getting errors complaining about "/etc/shadow" doesn't exist in pbuilder chroot, you are bitten by [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338976 Debian bug #338976]. Change your /usr/lib/pbuilder/pbuilder-buildpackage-funcs according to the patch at the end of bug report to work around this issue, and wait for pbuilder 0.139 getting merged.

Multiple pbuilders

When you work with packages, you often want to have multple pbuilders on your machine, if for example you want to backport to Breezy while developping on Dapper, or test packages on Sid to track bugs.

To do that, you can adapt the file in /usr/share/doc/pbuilder/examples/pbuilder-distribution.sh, which by default contains :

# script from Jamin W. Collins  BTS: #255165
# name this script 'pbuilder-woody', 'pbuilder-sid', 'pbuilder-sarge', 'pbuilder-experimental' etc.

OPERATION=$1
DISTRIBUTION=`basename $0 | cut -f2 -d '-'`
PROCEED=false
BASE_DIR="$HOME/pbuilder"
case $OPERATION in
   create|update|build|clean|login|execute )
      PROCEED=true
      ;;
esac
if ( $PROCEED == true ) then
   shift
   sudo pbuilder $OPERATION \
      --basetgz $BASE_DIR/$DISTRIBUTION-base.tgz \
      --distribution $DISTRIBUTION \
      --buildresult $BASE_DIR/result $@
else
   echo "Invalid command..."
   echo "Valid commands are:"
   echo "   create"
   echo "   update"
   echo "   build"
   echo "   clean"
   echo "   login"
   echo "   execute"
   exit 1
fi

Rename it to the distribution you want, e.g. pbuilder-dapper, then put it in /usr/local/bin/ Since /var/cache/pbuilder is the common directory used for pbuilders, I recommend changing the script to the following :

# script from Jamin W. Collins  BTS: #255165
# name this script 'pbuilder-woody', 'pbuilder-sid', 'pbuilder-sarge' etc.

OPERATION=$1
DISTRIBUTION=`basename $0 | cut -f2 -d '-'`
PROCEED=false
BASE_DIR="/var/cache/pbuilder"
case $OPERATION in
   create|update|build|clean|login|execute )
      PROCEED=true
      ;;
esac
if ( $PROCEED == true ) then
   shift
   sudo /usr/sbin/pbuilder $OPERATION \
      --basetgz $BASE_DIR/$DISTRIBUTION/base.tgz \
      --distribution $DISTRIBUTION \
      --configfile $BASE_DIR/$DISTRIBUTION/pbuilderrc \
      --aptconfdir $BASE_DIR/$DISTRIBUTION/apt.config \
      --buildresult $BASE_DIR/$DISTRIBUTION/result $@

if [[ "$OPERATION" = "build" ]]; then
   echo "Building local repository"
   /usr/local/bin/build-repository ubuntu $DISTRIBUTION
fi

else
   echo "Invalid command..."
   echo "Valid commands are:"
   echo "   create"
   echo "   update"
   echo "   build"
   echo "   clean"
   echo "   login"
   echo "   execute"
   exit 1
fi

Then you should create a /var/cache/pbuilder/DISTRIBUTION directory (e.g. /var/cache/pbuilder/dapper/), put the correct configuration files there (see the previous sections) then run pbuilder-dapper create to create the pbuilder in this location. You can then do the same for other distributions (e.g. pbuilder-breezy, pbuilder-sarge, pbuilder-sid, etc.).

Ubuntu Wiki