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 am trying to make my first bug fixing for Ubuntu. While following the fixing a bug instruction from fixing-a-bug and packaging: link via changelog on I have encountered a problem at the setup "Testing the fix".

While trying to build with bzr builddeb -- -S -us -uc, I have encountered below error message:

dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building totem using existing ./totem_3.0.1.orig.tar.gz
dpkg-source: error: cannot read totem-3.0.1.orig.B4x9vh/debian/patches/totem-1041032-fixed: No such file or directory
dpkg-buildpackage: error: dpkg-source -b totem-3.0.1 gave error exit status 2
debuild: fatal error at line 1350:
dpkg-buildpackage -rfakeroot -d -us -uc -S failed
bzr: ERROR: The build failed.

It seems there's no such folder totem-3.0.1.orig.B4x9vh.

I was stuck on not knowing why and how these folder would be generated under my Branching for a change.

share|improve this question
Could you update your question with the entire output from your attempt to build this package please? My guess is that a file that was generated and intended to go in one place has ended up in another somewhere along the line. – Chris Wilson Mar 6 '13 at 22:39

I have fixed this issue in other way and build the package in my environment.

Basically follow the steps given at packaging:link-via-changelog

Firstly, download the source code and create another branch. Run these commands:

bzr pull
bzr branch bug-12345

And then before making any changes, I need to go back to the source package and create an *.orig.tar.gz source package.

Simply change the directory to and run bzr bd -- -S -us -uc.

Then I could start modifying my changes in bug-12345. After modifying, I used dch -i and debcommit to commit the changes.

And then instead of using bzr command to generate the package, I used debuild/dpkg-buildpackage instead.

For generating pure source code package: I use debuild -S

And to generate a release binary build: I use dpkg-buildpackage.

Reference: dpkg-buildpakcage

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.