Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When my package gets build by launchpad using a recipe, it ignores the ./debian/changelog file I provide, and it generates a useless one like following:

harmonyseq (0.14~natty1) maverick; urgency=low

  * Auto build.
 -- Rafal Cieslak <>   Tue, 25 Jan 2011 16:56:57 +0000

It would be much better if launchpad stored the list of changes I prepared in the changelog file, rather than just putting "Auto build" there.

How do I force launchpad to use the list of changes from my changelog file, when building packages from a recipe?

share|improve this question
What are you using to trigger the builds? Under normal conditions, LP always uses the provided debian/changelog... – Kees Cook Mar 10 '11 at 21:36
The best place to ask this question is Launchpad itself. Asking it there will allow the developers and experienced people to explain exactly how to do it, or why it can't be done Launchpad has a special system to manage this type of questions, you can ask it here, where other people, including developers and users, will be able to answer you, or here, where the thing becomes more official. – sebikul Mar 10 '11 at 21:38
@KeesCook I can reproduce this. This new entry seems to get created when using a project.recipe to build the source file (locally via bzr dailydeb project.recipe working-dir where the recipe file just gets the source branch and nests the packaging information). – htorque Mar 11 '11 at 16:41
up vote 5 down vote accepted

I asked this question on IRC (at #launchpad) and got the answer I was expecting:

No, it's not possible to prevent the creation of that changelog entry. It is necessary so that it can specify the appropriate autobuild version string (the one you define in the first line of the recipe file).

However, your changes should not be lost, just placed right after that entry.

share|improve this answer
Perhaps bzr-builder should integrate the autobuild changelog entry with any existing entry with the distribution set to UNRELEASED, as is common in debian changelog files. – jelmer Mar 14 '11 at 1:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.