From owner-freebsd-ports@FreeBSD.ORG Mon Jul 21 09:48:07 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E4C1065671 for ; Mon, 21 Jul 2008 09:48:07 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4D08FC19 for ; Mon, 21 Jul 2008 09:48:06 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from sleuth64 (unknown [192.168.15.142]) by dns1.vizion2000.net (Postfix) with ESMTP id 841271CC44; Mon, 21 Jul 2008 03:09:50 -0700 (PDT) From: To: References: <278e8bc1-ae13-4c8c-8d2e-cd9c0174b4af@8g2000hse.googlegroups.com> Date: Mon, 21 Jul 2008 02:48:04 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcjpznN69Qvte0/7RASev4QjrTRf+wBRmvrg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133 In-Reply-To: Cc: freebsd-ports@freebsd.org Subject: Patch failure for Ruby18-gems-1.2.0 on amd64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2008 09:48:07 -0000 Following error message: ===> Patching for ruby18-gems-1.2.0 ===> ruby18-gems-1.2.0 depends on file: /usr/local/bin/ruby18 - found ===> Applying FreeBSD patches for ruby18-gems-1.2.0 => Patch patch-lib-rubygems-source_info_cache.rb failed to apply cleanly. *** Error code 1 Stop in /usr/ports/devel/ruby-gems FreeBSD ***.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 @***.vizion2000.net:/usr/obj/usr/src/sys/GENERIC amd64 This system has just been upgraded from 6.3 to 7.0-Stable. Is there a possible connection here? After getting this error I checked to make sure the port tree was uptofate and tried again with the same result. I am currently recompiling ruby* ports on the system after a portsclean with: portupgrade -fr ruby* Has anyone else experienced a similar problem? I will report result of recompile when it finishes. David