dpkg-source regression when a patch removes all files from a directory
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Ubuntu) |
Fix Released
|
Medium
|
Barry Warsaw | ||
| Quantal |
Fix Released
|
Medium
|
Barry Warsaw | ||
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.
dpkg-source: info: building ruby1.9.1 in ruby1.9.
dpkg-source: info: building ruby1.9.1 in ruby1.9.
dpkg-genchanges -S >../ruby1.
dpkg-genchanges: not including original source code in upload
dpkg-source --after-build ruby1.9.1-1.9.3.194
dpkg-source: error: failed to copy ruby1.9.
dpkg-source: info: unapplying 20120927-
dpkg-buildpackage: error: dpkg-source --after-build ruby1.9.1-1.9.3.194 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 reproducer.
Related branches
| Tyler Hicks (tyhicks) wrote | #1 |
| Changed in dpkg (Ubuntu): | |
| assignee: | Tyler Hicks (tyhicks) → nobody |
| status: | In Progress → Confirmed |
| tags: | added: quantal regression-release |
| Changed in dpkg (Ubuntu Quantal): | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Barry Warsaw (barry) |
| milestone: | none → ubuntu-12.10 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in dpkg (Ubuntu Quantal): | |
| status: | In Progress → Fix Released |
Passes test case found in the Debian bug. Also passes the simple tests in test-dpkg.py from the qa-regression-
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.
Thanks!