Source build based on recipe fails with the error 'sh: Bad substitution'

Bug #604837 reported by Matthieu Baerts
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Unassigned
pbuilder (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hello,

I'm currently preparing some 'recipes' for the Cairo-Dock project.
It works great for the 'Core' part for Lucid series: https://code.edge.launchpad.net/~matttbe/+recipe/cairo-dock-test-build-lucid
But not for its plug-ins: https://code.edge.launchpad.net/~matttbe/+recipe/cairo-dock-plug-ins-test-build-lucid
I've this error only if I launch the 'recipe' on LaunchPad for Lucid series: "sh: Bad substitution" (the full buildlog.txt is available there: http://launchpadlibrarian.net/51790437/buildlog.txt.gz). It's a bit strange because I don't have any error if I try this 'recipe' locally (on Ubuntu Maverick 64bits) with this command:
    $ bzr dailydeb cairo-dock-plug-ins.recipe test/
and this is the content of cairo-dock-plug-ins.recipe:
    # bzr-builder format 0.2 deb-version 2.2.0-0beta2-{revno:core}-0ubuntu1~ppa0~lucid
    lp:cairo-dock-plug-ins
    nest packaging lp:~cairo-dock-team/cairo-dock-plug-ins/debian-dailydeb-lucid-plug-ins debian
    nest core lp:cairo-dock-core tmp
Can I use two 'nest' commands for Lucid series?

Thank you for this great tool!

PS: Cairo-Dock Core is an API and Cairo-Dock Plug-ins uses this API. So the latest revision of the Plug-ins branch has to be compiled with the latest version of the Core branch. This is why I've to add this line in the recipe file:
     nest core lp:cairo-dock-core tmp
only to use "{revno:core}" and having the same deb-version for the both packages.

Tags: lp-code recipe
Revision history for this message
Tim Penhey (thumper) wrote :

What version of bzr-builder are you using locally to test? If it is from the trunk branch, what is the tip revno?

tags: added: recipe
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Sorry, I forgot to say that I've installed 'bzr-builder' package from this ppa: https://launchpad.net/~dailydebs-team/+archive/bzr-builder
So it seems it seems I use the revision 79.
But I can download the latest revision of the branch lp:bzr-builder if you want!

Revision history for this message
Aaron Bentley (abentley) wrote :

bzr-builder is running to completion. It's pbuilder or a later step that's causing this failure.

Revision history for this message
Loïc Minier (lool) wrote :

Which piece of code is calling pbuilder-satisfy-depends?

Revision history for this message
Matthieu Baerts (matttbe) wrote :

Thank you, it's seems it's fixed!

PS: Do you know when a new version of bzr-builder will be updated? Because I need the "{date}" variable in order to completely automate the process and prevent some compilation errors :)

Changed in pbuilder (Ubuntu):
status: New → Invalid
Changed in launchpad-code:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.