workflow advice for bzr builder + pbuilder

[James Westby]

On Mon, 23 Apr 2012 09:03:19 +0200, Tim Michelsen <timmichelsen at gmx-topmail.de> wrote:
> Hello,
> I am packaging some cutting edge Scipy/Numpy addon packages to a PPA.
> I frequently encounter problems (build failues) because something in the 
> upstream changes.
> 
> I am using recipies on LP.
> 
> Now I want to use a local environment to debug faster.
> 
> Could you please advise me on a efficient workflow that uses bzr 
> builddeb and pbuilder for this?
> 
> another user apparently was in the same situation:
> 
> http://irclogs.ubuntu.com/2012/03/27/%23launchpad.txt
> 
> [20:58] <audifahrer> dobey: yes, I use a receipe. I don't use pbuilder 
> localy until now.
> [21:01] <dobey> audifahrer: ok, you can use bzr dailydeb to get a source 
> package for a recipe, and then you would use pbuilder to build that 
> source package in a local chroot
> [21:01] <dobey> audifahrer: and you can debug it there, instead of 
> constantly trying to rebuild it on launchpad

Hi,

If you grab the text of your recipe from Launchpad and save it in a text
file then you can run

  bzr dailydeb <that file>

if you have bzr-builder installed, and it will either spit out a source
package that you can pass to pbuilder

  pbuilder <package>.dsc

or tell you the error in building the source package.

Thanks,

James