launchpad recipe fails without certain files. Curious if this is normal behaviour or a bug
In order to get a launchpad recipe not to fail I have to upload the following files which it seems should be unnecessary:
*.in (for instance, Makefile.in, header.h.in, etc)
aclocal.m4
install-sh
configure
debcomp (not absolutely sure if this is really needed - added because install-sh was needed)
missing (ditto above explanation for debcomp)
src/*.in
man/*.in
It would seem all these auto-generated files could/should be generated automatically by the build system in launchpad, not uploaded from the local user's files. Is this normal and expected, or does launchpad need to be updated in this regard?
Here is my code: http://
Also, before I got to the point of figuring out I had to include all these files, I found that if I had any quilt patch files, the build failed - this current bug on this seems to apply: https:/
The above problem also happens on the following project: https:/
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- William Grant
- Solved:
- 2011-09-24
- Last query:
- 2011-09-24
- Last reply:
- 2011-09-24
|
|
#1 |
We sorted this out on IRC with dh-autoreconf, and it all seems to work now.
William Grant is correct - by adding "--with autoreconf" in the debian/rules file as follows:
dh --with autoreconf $@
The recipe (e.g., debhelper) uses dh-autoreconf to produce all the necessary auto-generated files, including the .orig.tar.gz file, from just the base source and configuration files hand coded or customised. This lead to a very clean tree in bazaar and on launchpad.
However, to bring in the dh-autoreconf tools into the toolchain used by the recipe, I had to add ", dh-autoreconf" to the Build-Depends line in the debian/control file (recipe failed until I did this):
Build-Depends: debhelper (>= 7.0.50~), autotools-dev, dh-autoreconf
You can see how clean and minimal the files now necessary to build the recipe are here:
http://
