patch not applied - driving me crazy!

Edwin Groothuis edwin at
Sat Apr 5 02:10:41 PST 2003


This is driving me crazy, I have one (1) patch, created by myself
with diff -u, happily stored in files/, cleanly detected by the
ports-framework which refuses to be applied:

    [~/ports/NEW/ccmalloc] edwin at ref5>PATCH_DEBUG=1 make patch
    ===>  Extracting for ccmalloc-0.3.9_1
    >> Checksum OK for ccmalloc-0.3.9.tar.gz.
    ===>  Patching for ccmalloc-0.3.9_1
    ===>  Applying FreeBSD patches for ccmalloc-0.3.9_1
    ===>   Applying FreeBSD patch /local0/scratch/edwin/ports/NEW/ccmalloc/files/
    Hmm...  Looks like a unified diff to me...
    The text leading up to this was:
    |--- src/       Wed Jan 30 06:23:55 2002
    |+++ src/    Sat Apr  5 02:05:19 2003
    File to patch: ____

At ____ it is waiting for me to fill in the name of a file.
Of which I copy and paste the name provided: src/
At that moment patch says "Excellent choice":

    Patching file src/ using Plan A...
    Hunk #1 succeeded at 9.
    Hunk #2 succeeded at 111.

Why oh why does this thing not want to be applied voluntarely? Has
anybody ever seen such behaviour?

Edwin, unable to comprehend this weird behaviour.

Edwin Groothuis      |            Personal website:
edwin at    |    Weblog: 

More information about the freebsd-ports mailing list