launchpad-users team mailing list archive

[Gianfranco Costamagna <costamagnagianfranco@xxxxxxxx>]

The "break" you posted was actually a succeed.

there is a two phase build, and that one is just the first pass.

The second one is the architecture dependent build, that you can find from the recipe, by clicking on the published ppa


https://code.launchpad.net/~sascha-manns-h/+recipe/daps-daily

https://code.launchpad.net/~sascha-manns-h/+archive/ubuntu/daps

and on "packages details"

https://code.launchpad.net/~sascha-manns-h/+archive/ubuntu/daps/+packages

clicking a random build log says
"

checking python module: lxml... yes
configure: ===== Checking for DocBook...
checking for -//OASIS//DTD DocBook XML V4.1.2//EN... no
checking for -//OASIS//DTD DocBook XML V4.2//EN... no
checking for -//OASIS//DTD DocBook XML V4.3//EN... no
checking for -//OASIS//DTD DocBook XML V4.4//EN... no
checking for -//OASIS//DTD DocBook XML V4.5//EN... no
configure: error: No DocBook 4 DTD not found
debian/rules:12: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory '/build/buildd/daps-1.9.22'
debian/rules:9: recipe for target 'build-arch' failed

"


missing some docbook-* b-d?

btw using local pbuilder-dist rather than lp (until the build succeedes) gives you two benefits:
-you don't loose time waiting for lp
-you can rebuild the same version, because lp doesn't allow you to publish twice the same revision (even if failed), so you will need to bump the debian revision or the upstream one in order to succeed

or maybe just wait for the next upstream commit :)

 
Just my 0.02 $ 

Gianfranco