Server Fault is a question and answer site for system and network administrators. 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

I'm starting to manage more custom-packaged applications for our Ubuntu Hardy systems. Some are of apps not available in Ubuntu but most are much newer versions than are available via the standard "-backports" process.

I'm trying to settle on the best way to manage these packages in subversion. One thought is just to commit the dpkg-buildpackage generated diff. Has anyone found a better way?

share|improve this question
up vote 5 down vote accepted

If you want to use subversion, use svn-buildpackage. There are also bzr-buildpackage, git-buildpackage, and so on. These all work similarly; you store either the full original source plus debian/ in version control, or only debian/ (which in turn might contain your patches).

If you are dealing with Ubuntu packages, it would make some sense to use bzr, because then you can easily branch and merge with the original Ubuntu bzr repositories.

share|improve this answer

You could use bzr-buildpackage. It has a nice guide at

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.