Subject: Re: pkg/29026
To: None <veego@netbsd.org, gnats-admin@netbsd.org, pkgsrc-bugs@netbsd.org>
From: John D. Baker <jdbaker@mylinuxisp.com>
List: pkgsrc-bugs
Date: 06/29/2005 23:35:01
The following reply was made to PR pkg/29026; it has been noted by GNATS.

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: Bernd Ernesti <veego@netbsd.org>
Cc: gnats-bugs@netbsd.org
Subject: Re: pkg/29026
Date: Wed, 29 Jun 2005 18:34:16 -0500 (CDT)

 On Wed, 29 Jun 2005, Bernd Ernesti wrote:
 
 > But it made it into 29939, and there i told you it is a problem with your
 > patch and asked on tech-pkg if someone has an idea how to solve the problem
 > with the RCS Id.
 
 I guess I forgot to edit the subject line again...
 
 I didn't quite understand what you meant when you sent that, but I think
 I do now.  Unless I am mistaken, by 'problem with your patch', I take
 it that you are suggesting there is a problem with the '/usr/bin/patch'
 executable on my systems.
 
 I would find that very difficult to believe.  Of the many, many packages
 I have built from pkgsrc on MacOS X, 10.1, 10.2, 10.3, and 10.4, the patch
 file 'comms/minicom/patches/patch-ae' is the first to cause a problem.
 Still, there were no problems building on NetBSD/i386-3.99.3.
 
 > You could maybe try the attached file instead of the current one and
 > do a make mps in the minicom to update the distinfo file and then try
 > to build it again.
 
 I replaced the comms/minicom/patches/patch-ae file with the one you
 attached.  I didn't bother generating a new SHA1 signature to put in
 the 'distinfo' file, since none of the other patch files' SHA1 signatures
 match what's in the 'distinfo' file anyway.
 
 The patch step emitted the following:
 
 [...]
 ===> Patching for minicom-2.1
 ===> Applying pkgsrc patches for minicom-2.1
 **************************************
 Patch file /usr/pkgsrc/comms/minicom/patches/patch-ae has been modified
 **************************************
 => Fixing hardcoded paths.
 [...]
 
 but went ahead with patching and building without any further complaint.
 I tested on both MacOS X 10.2.8 and 10.3.9.  I no-longer have any machines
 running 10.1.x.
 
 -- 
 John D. Baker, KN5UKS                    NetBSD     Darwin/MacOS X
 jdbaker(at)mylinuxisp(dot)com                 OpenBSD            FreeBSD
 BSD -- It just sits there and _works_!