From owner-freebsd-questions@FreeBSD.ORG Mon Jun 6 02:29:37 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07F1E16A41C for ; Mon, 6 Jun 2005 02:29:37 +0000 (GMT) (envelope-from freebsd.ml@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9304F43D5C for ; Mon, 6 Jun 2005 02:29:36 +0000 (GMT) (envelope-from freebsd.ml@gmail.com) Received: by wproxy.gmail.com with SMTP id 49so217739wri for ; Sun, 05 Jun 2005 19:29:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BhYOhMJ8ToNI3Iqblt82cCNlfVQbqBU8VGm6GduUc7Z5YD6iajKHYRkIOpGnmkIARY4iFn4OtUeK3WO0+Zv+J6g7xW00txvrkGUI4GHAzBZkt+w6AiilZ0EpKmE8sZkGmnapzU9j12xTtLPxVSMHnQShHylKvYx8oKboPrUmveE= Received: by 10.54.17.70 with SMTP id 70mr138296wrq; Sun, 05 Jun 2005 19:29:35 -0700 (PDT) Received: by 10.54.20.41 with HTTP; Sun, 5 Jun 2005 19:29:35 -0700 (PDT) Message-ID: Date: Mon, 6 Jun 2005 11:29:35 +0900 From: FreeBSD MailingLists To: Kris Kennaway In-Reply-To: <20050606010129.GA57493@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050605170340.GA14827@gothmog.gr> <20050606010129.GA57493@xor.obsecurity.org> Cc: questions Subject: Re: patch errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD MailingLists List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 02:29:37 -0000 on all other servers I cvsup the src and ports tree, but for some reason the internet connection at the location of this particular server gets kicked when I start cvsup. so I had to resort to this method. I am not entirely convinced that it is a stale patch issue for 2 reasons. 1) I have untar'd the same file on 2 different servers and only this one has issues updating the ports 2) I have tar'd up the /usr/ports dir from a different server that updates via cvsup. The original server updates fine but when untar'd on this particular server the same exact patch errors appear. which leads me to believe the error is outside the ports tree itself. -tomoki On 6/6/05, Kris Kennaway wrote: > On Mon, Jun 06, 2005 at 09:46:35AM +0900, FreeBSD MailingLists wrote: > > Yes, Everyday I try this I grab the latest copy of ports.tar.gz from a > > near by server. The file is updated daily. and using the same tar > > file on other machine results in no errors. I am thinking that my > > patch program is messed up, since all the error s are patch errors, > > either it can't find the file to patch or the file cannot be patched > > correctly. >=20 > The problem is almost certainlythat you have stale patches in your > tree. Consider what will happen with your "upgrade" mechanism when a > patch file is deleted from the ports tree. >=20 > There are much better ways to update your ports collection than this. >=20 > Kris >=20 >=20 >