From owner-freebsd-ports@FreeBSD.ORG Fri Feb 18 07:01:23 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66CBC16A4CE for ; Fri, 18 Feb 2005 07:01:23 +0000 (GMT) Received: from smtp807.mail.sc5.yahoo.com (smtp807.mail.sc5.yahoo.com [66.163.168.186]) by mx1.FreeBSD.org (Postfix) with SMTP id F1A6E43D2F for ; Fri, 18 Feb 2005 07:01:22 +0000 (GMT) (envelope-from krinklyfig@spymac.com) Received: from unknown (HELO smogmonster.com) (jtinnin@pacbell.net@64.173.27.163 with login) by smtp807.mail.sc5.yahoo.com with SMTP; 18 Feb 2005 07:01:22 -0000 From: Joshua Tinnin To: freebsd-ports@freebsd.org Date: Thu, 17 Feb 2005 23:01:20 -0800 User-Agent: KMail/1.7.2 References: <20050217190549.72c4eb4d@dolphin.local.net> <006201c51582$980f04a0$7702a8c0@officeeagle> <1108708501.71774.3.camel@dirk.no.domain> In-Reply-To: <1108708501.71774.3.camel@dirk.no.domain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502172301.21173.krinklyfig@spymac.com> cc: Paul Schmehl cc: Sam Lawrance Subject: Re: patching? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 07:01:23 -0000 On Thursday 17 February 2005 10:35 pm, Sam Lawrance 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