Hi,
> 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.
I usually run dpatch-edit-patch for each patch file, and fix rejects when
it fails to apply.
However, a dry-run option looks like it might be useful, yes.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
