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

From my point of view at the moment git-buildpackage is only intended for using upstream sources which are not in the same repository. I already have a git-buildpackage repository with the branches "master", "upstream and a tags from the initial import via git-import-orig.

I cant find a howto, to have a development branch in the repository and import the changes from there into the upstream branch and make it buildable by git-buildpackage. I think the answer lies behind the steps git-import-orig does with the repository, which i dont know yet.

Any suggestions about having one repository which is git-buildpacke compliant and can be used to

share|improve this question
up vote 1 down vote accepted

Actually, there is a section in the git-buildpackage documentation matching your use case.

Basically, the difference is that, when importing a new release into your debian branch, you will merge modifications from a tag corresponding to the new release of your software instead of a tarball. As no tarball is involved, there is no need to use git-import-orig.

Just make sure that your branches and tag naming matches what git-buildpackage expects. If this is not the case, you will have to override the default configuration with your own configuration file. The syntax is explained in the documentation and the configuration file is searched at various locations. See git-buildpackage man page to know where (section CONFIGURATION FILES).

share|improve this answer

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.