On Thu, Jun 16, 2005 at 06:46:04PM +0200, Daniel Leidert wrote:
> Let's say, we are working in the source tree of a Debian package and ran
> build target, so the patch/patch-stamp target was called. The source is
> now patched. Now you maybe see a mistake and you want to edit an
> existing patch. Running dpatch-edit-patch, modifying and saving the
> patch now leads to the following situation: The patch is modified in
> debian/patches, but the old patch is still applied to the source, because
> the clean target (unpatch target) is applied to the directoty in /tmp,
> not to the real source. Trying to call the unpatch target (e.g. with the clean
> target) now fails, because the patch cannot be reverted. The only chance to
> run unpatch target is to apply manually the changes made during the last
> patch-change to the source too, fix debian/patched and then try to call
> unpatch target again. Maybe dpatch-edit-patch should check for the
> existence of debian/patched inside the source and apply the unpatch
> target to the source if debian/patched is found.

I do not quite understand what you mean. Can you give a trivial
example, preferably in form of a typescript?

dpep copies your current source to the "reference copy", and then runs
debian/rules clean in the reference copy. The reference copy is then
copied once more to the work copy, which you edit. After exiting the
shell, the diff between reference copy and work copy is then saved to
the patch file name.

The invocation of the debian/rules clean target after creating the
reference copy should remove all your patches so that you start from a
clean copy.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to