[Bug 1057886] Re: dpkg-source regression when a patch removes all files from a directory

Tyler Hicks tyhicks at canonical.com
Fri Sep 28 06:12:43 UTC 2012

Passes test case found in the Debian bug. Also passes the simple tests
in test-dpkg.py from the qa-regression-testing project.

To be clear, I do not need this fix to proceed with the update mentioned
in this bug description. I've found a different/better way to do what I
needed to do but since I did hit this bug, I figured it would be good to
get the fix in to Ubuntu's dpkg before someone else hits it.


** Patch added: "dpkg_1.16.7ubuntu5.debdiff"

** Changed in: dpkg (Ubuntu)
       Status: In Progress => Confirmed

** Changed in: dpkg (Ubuntu)
     Assignee: Tyler Hicks (tyhicks) => (unassigned)

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.

  dpkg-source regression when a patch removes all files from a directory

Status in “dpkg” package in Ubuntu:

Bug description:
  I was recently working on a package update and created a patch which
  deleted all files in a directory. When I tried to build the package, I
  hit an unexpected dpkg-source error:

  dpkg-source: info: using source format `3.0 (quilt)'
  dpkg-source: info: building ruby1.9.1 using existing ./ruby1.9.1_1.9.3.194.orig.tar.gz
  dpkg-source: info: building ruby1.9.1 in ruby1.9.1_1.9.3.194-1ubuntu1.debian.tar.gz
  dpkg-source: info: building ruby1.9.1 in ruby1.9.1_1.9.3.194-1ubuntu1.dsc
   dpkg-genchanges -S >../ruby1.9.1_1.9.3.194-1ubuntu1_source.changes
  dpkg-genchanges: not including original source code in upload
   dpkg-source --after-build ruby1.9.1-
  dpkg-source: error: failed to copy ruby1.9.1- to ruby1.9.1- No such file or directory
  dpkg-source: info: unapplying 20120927-rubygems_disable_upstream_certs.patch
  dpkg-buildpackage: error: dpkg-source --after-build ruby1.9.1- gave error exit status 2
  debuild: fatal error at line 1357:
  dpkg-buildpackage -rfakeroot -d -us -uc -S failed

  After doing some research, I found that it is a known bug and has a
  fix applied in upstream dpkg. The Debian bug report also has a


To manage notifications about this bug go to:

More information about the foundations-bugs mailing list