Launchpad itself

pbuilder-satisfydepends-dummy incorrectly empty in daily recipe

Asked by Boris Dušek

Hello,

I am creating a daily recipe for gnome-orca [1]. The package builds fine locally using bzr dailydeb + pbuilder build *.dsc. But when I setup the recipe on launchpad, it exhibited build failure [2], which I pinpointed to the fact that the source package build process does not install build dependencies, or more precisely, the "pbuilder-satisfydepends-dummy" package has no dependencies. These missing dependencies then cause "debian/rules clean" to fail.

I don't know if I am doing something wrong, or if it's a bug somewhere in the launchpad infrastructure, or if the cause is something else than what I am suggesting.

Thanks for any suggestions.

[1]: https://code.launchpad.net/~dusek/+recipe/gnome-orca-daily
[2]: https://launchpadlibrarian.net/68119042/buildlog.txt.gz

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Max Bowsher
Solved:
Last query:
Last reply:
Revision history for this message
Best Max Bowsher (maxb) said : 		#1

The problem is the blank line in your debian/control file separating the commented out block and the initial "Source: gnome-orca" paragraph. A very strict reading of the Debian Policy Manual says this is invalid: you have an empty initial paragraph, and the Source paragraph as the second paragraph. Some tools may be more tolerant and skip the initial empty paragraph, however pbuilder-satisfydepends does not. (And I would not particularly want to attempt to fix that, given that its parser is a fairly fiendish sed script!)

Revision history for this message
Boris Dušek (dusek) said : 		#2

Thank you very much for the timely and precise response Max! That was really the problem, after removing the comment it's now building fine.

Revision history for this message
Boris Dušek (dusek) said : 		#3

Thanks Max Bowsher, that solved my question.

Revision history for this message
Max Bowsher (maxb) said : 		#4

Glad to hear it works.

For the record, you *can* have a comment there - you must just ensure there is no blank line between the last line of the comment and the "Source: ..." line.