daily build failure: unmet build dependencies

[Pim Vullers]

Since recently I started receiving daily build reports. And unfortunately they contain failures. I just looked into it and it seems to be caused by missing dependencies:

dpkg-checkbuilddeps: Unmet build dependencies: cmake (>= 2.6) debhelper (>= 7.0.50~) libclutter-gst-dev libclutter-gtk-1.0-dev libgranite-dev libgtk-3-dev (>= 3.0) valac (>= 0.15.2) libgstreamer-plugins-base0.10-dev
dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: warning: (Use -d flag to override.)
dpkg-buildpackage: warning: This is currently a non-fatal warning with -S, but
dpkg-buildpackage: warning: will probably become fatal in the future.
 fakeroot debian/rules clean
dh clean
make: dh: Command not found
make: *** [clean] Error 127
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

I do not know who set this up, but it seems that the configuration should be changed. For example I'm wondering why we need valac 0.15.2...

[Cody Garver (codygarver)]

It's funny you should mention that, I've been away a bit and I JUST noticed and started tweaking that. It'll be a while on the PPA build to see if I straightened it out properly (since I haven't had time to master multiple custom sources on my local build system). Thanks for the report, Pim!

[Alin Andrei (nilarimogard)]

I see it's still failing... you can add the Vala PPA ( https://launchpad.net/~vala-team/+archive/ppa ) as a dependency for the Audience PPA.

[Pim Vullers (pimvullers)]

This PPA was actually added already. But to me it seemed that the package name in the dependencies list was wrong... I updated it now and am trying to build again.

[Pim Vullers (pimvullers)]

BTW. What do you think about splitting out the deb-packaging information into a seperate branch and then use the recipe to merge them to allow launchpad to build the .deb files (like it is done in most other elementary projects)?

[Pim Vullers (pimvullers)]

The main issue seems to be solved right now. The recipe now produces source archives for audience. The only comment I have on those is that the top folder contained in those is called recipe-{debupstream}-0~{revno} instead of audience (perhaps with a version number like -0.1)...

The remaining part is to have launchpad actually build audience to create a binary. As you might know, I'm not on an ubuntu system, so I cannot try this out easily. So could somebody else look into this further?

[Pim Vullers (pimvullers)]

Just as a sidenote, do we actually need different tarballs for source releases? These do not differ for the various ubuntu version, not even for Linux distributions. In my opinion audience-0.1.tar.gz would be sufficient (optionally with a ~rev to include the revision for the daily builds).

[Cody Garver (codygarver)]

Pim, I've moved the debian packaging to lp:~audience-members/audience/deb-packaging

Good eye spotting the mislabeled package. Make whatever changes you see fit regarding the tars. Mark this bug fixed when you're satisfied.

[Pim Vullers (pimvullers)]

Cody, I do not know what the original intention was, should the daily builds also produce binaries or not? If so, I can look into the source archives, but somebody on an ubuntu system will have to take care of the binary packages.