Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Feb 2005 23:01:20 -0800
From:      Joshua Tinnin <krinklyfig@spymac.com>
To:        freebsd-ports@freebsd.org
Cc:        Sam Lawrance <boris@brooknet.com.au>
Subject:   Re: patching?
Message-ID:  <200502172301.21173.krinklyfig@spymac.com>
In-Reply-To: <1108708501.71774.3.camel@dirk.no.domain>
References:  <20050217190549.72c4eb4d@dolphin.local.net> <006201c51582$980f04a0$7702a8c0@officeeagle> <1108708501.71774.3.camel@dirk.no.domain>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 17 February 2005 10:35 pm, Sam Lawrance 
<boris@brooknet.com.au> wrote:
> On Fri, 2005-02-18 at 00:24 -0600, Paul Schmehl wrote:
> >  make install
> > ===>  Extracting for sguil-server-0.5.3
> > => Checksum OK for sguil-server-0.5.3.tar.gz.
> > ===>  Patching for sguil-server-0.5.3
> > ===>  Applying FreeBSD patches for sguil-server-0.5.3
> > Ignoring previously applied (or reversed) patch.
> > 1 out of 1 hunks ignored--saving rejects to
> > server/archive_sguildb.tcl.rej => Patch patch-archive_sguildb.tcl
> > failed to apply cleanly. *** Error code 1
>
> As the error says, are the patches reversed? ie. perhaps you have
> incorrectly run
>
> 	diff -urN file file.orig
>
> instead of the correct
>
> 	diff -urN file.orig file

Sometimes I get this problem if I forget to use the -p flag when 
patching (from the /usr/ports/ directory):

# patch -p0 < /path/to/patchfile

But this also depends on how the patch is written. You might already 
know how to patch, but what the heck. The first time I made a patch I 
did it incorrectly and reversed it when running diff, like Sam's 
example above.

- jt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502172301.21173.krinklyfig>