Package: dpatch Version: 2.0.18 Severity: normal Hello,
yesterday I have been confused by dpatch again. Usually, on usptream version updates, I run dpatch on all to see which dpatch fails first, then I unpatch it all and run d-p-e on the patch that failed. This technique usually works. However, there are cases where patch -R wreaks random havoc and "reverts" more stuff that the previous patch effort did change. So I end up with modified upstream files while dpatch system is still considering this state as "pristine upstream source". There is no good workaround when using the update method described above. But what certainly would help is a dry-run command, applying all patches (eg. merging then all and using --dry-run or so, or applying the chain in parts on a temporary copy) and see which fails first. Eduard. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-amd64-k8 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) dpatch depends on no packages. Versions of packages dpatch recommends: ii dpkg-dev 1.13.16 package building tools for Debian ii fakeroot 1.5.7 Gives a fake root environment ii patchutils 0.2.31-3 Utilities to work with patches -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
