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

I'm creating customized binary versions of OpenStack nova packages (lp:nova) using their packaging scripts (lp:~openstack-ubuntu-packagers/ubuntu/natty/nova/ubuntu).

I create binaries by doing:

dpkg-buildpackage -b -rfakeroot -tc -uc -D

This creates a set of packages (python-nova, nova-common, nova-compute, ...).

In our customized version of the code (lp:~usc-isi/nova/hpc-trunk), we recently merged in some changes from another branch, and there's now a new file in our repository that wasn't in upstream: nova/virt/cpuinfo.xml.template.

This file isn't getting added to any of the packages, where it should be added to python-nova.

Why wouldn't dpkg-buildpackage be including this file? A more basic question: how does dpkg-buildpackage determine which files go in which packages? Is it related at all to the debian/watch file? This contains some URLs that are pointing to the upstream project.

version=3*/nova-(.*)\.tar\.gz nova-(.*).tar.gz
share|improve this question
log/watch is not related, it just defines how to check for new versions of the source distribution. – Adam Byrtek Mar 14 '11 at 23:13

I didn't notice the file in the top-level of the source tree (not in debian directory).

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.