Tag Archives: pbuilder

Execute module-assistant into pbuilder

Like promised, this post doesn’t start with rivendell ;-)

The first objective was testing the module source packages provided with Rivendell. Between etch and intrepid, these modules can be built on several kernel versions (from 2.6.18 to 2.6.27) and waiting errors on the rivendell user mailing-list doesn”t seem a good solution :-)

So, I looked for a way to execute module assistant into pbuilder. pbuilder has a command “execute” which takes a script, copy and execute it into the chroot. execute-module-assistant was borned.

Continue reading →

Integrate debian-multimedia into pbuilder

By making the streamTranscoder package, I have to modify my pbuilder configuration to integrate the debian-multimedia repository.

The operation is simple : Update the pbuilder image with the repository definition in the OTHERMIRROR into the pbuilderrc file. Use a “|” separator between repositories if needed.

OTHERMIRROR="...|deb http://mirror.home-dn.net/debian-multimedia sarge main"

Same thing if you’re using the --othermirror option.

And don’t forget the –override-config option to the update command line.

my first pbuilder build

After one hundred tries, pbuilder has finally built a libradio package.

Some notes about this new experience:

  • when adding a deb line into OTHERMIRROR, you need to recreate the base file, the apt sources.list isn’t modified else
  • add a D10apt-get-update to your hooks directory which runs “apt-get update” to use the lastest apt indexes for build dependencies
  • read the useful pbuilder User’s Manual

debian packaging is a way of life

My CPU is burning for several hours. I’m trying to make the rivendell package cleaner and I’m going to go crazy with the debian packaging tools :-/ The 50th rivendell build is now running .. and I’ve experienced 2 or 3 dozen of various problems with dpkg-source, pbuilder, debarchiver and cie. Debian packaging is a very pretty environment but it’s sometimes a obscur science :-)

There are some notes from my day troubles:

  • debuild, the wrapper of wrapper: it’s a wrapper for dpkg-buildpkg .. which wraps several dpkg tools
  • use cdebootsrap with pbuilder (instead of the debootstrap), either you can’t build an etch or sid base
  • if your package doesn’t end with -0 or -1, the orig.tar.gz won’t be specified into the changes file, use the -sa option of dpkg-source
  • if your debarchiver moves your incoming files into a REJECT directory, set the --debug-level to 4 to know more. In my case, the changes file was invalid and designated the wrong tar.gz. Note that logcheck considerates “debug” as a keyword for .. security event .. so fix the logcheck rules to avoid a mail spamming.

My pending problems are:

  • how run pbuilder without running a whole dpkg-buildpackage ? Because pbuilder uses the files created by dpkg-buildpackage .. and when you need to check the Build-Depends of your package .. it takes the night :-(
  • how inject my gpg key passphrase to debuild ? via a customized gpg command, or something like ?
  • something dpkg-buildpackage fails after the initial dpkg-source -b for an unknown reason ..

I’ve read and I read again the Debian New Maintainers’ Guide .. but many things are missing in this Debian bible ;-)

Next step .. study cdbs .. and discover a lot of new things :-)