Hi!
I think at the time it seemed quick to fix, but when I actually looked,
it wasn't. In the mean time, through another (related) report, I improved
the error message which now reads as follows:
,---
[…]
dpkg-source: info: applying debian-changes.patch
patching file debian/rules
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch 'debian-changes.patch' is correctly applied by quilt, use 'quilt refresh' to update it
dpkg-source: info: if the file is present in the unpacked source, make sure it is also present in the orig tarball
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/debian-changes.patch/ --reject-file=- < source-1.0.orig._XkvRm/debian/patches/debian-changes.patch subprocess returned exit status 1
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
`---
Where it is now hinted that patching a file that is not present in the
orig tarball will fail. I think this is an improvement, that covers
this case too, although perhaps it's not entirely obvious to a newcomer.
Ideally, the patch would get parsed, and any hunk modifying or
deleting (instead of adding) a file that is not present in the orig
tarball would be detected and handled on its own, but I'm afraid that
will need more work here.
Thanks,
Guillem