From owner-freebsd-ports@FreeBSD.ORG Sun Jan 18 01:54:02 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 83AE7106566B for ; Sun, 18 Jan 2009 01:54:02 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id 3910F150F76 for ; Sun, 18 Jan 2009 01:54:01 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: (qmail 42440 invoked from network); 18 Jan 2009 01:51:12 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2009 01:51:12 -0000 Message-ID: <49728B10.4080808@freebsd.org> Date: Sat, 17 Jan 2009 17:51:12 -0800 From: Colin Percival User-Agent: Thunderbird 2.0.0.17 (X11/20081002) MIME-Version: 1.0 To: Garrett Cooper References: <7d6fde3d0901171349o20f1b8d2x944bcae5394b8eb9@mail.gmail.com> <49725E61.6070701@freebsd.org> <7d6fde3d0901171557v4e2d6e9enc564c8bdab100931@mail.gmail.com> In-Reply-To: <7d6fde3d0901171557v4e2d6e9enc564c8bdab100931@mail.gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Subject: Re: textproc/libxml2 and failed patching after using portsnap... 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: Sun, 18 Jan 2009 01:54:02 -0000 Garrett Cooper wrote: > On Sat, Jan 17, 2009 at 2:40 PM, Colin Percival wrote: >> Garrett Cooper wrote: >>> This is just a notice that a patch is no longer needed with >>> textproc/libxml2 -- it appears to have been checked in upstream: >>> >>> This isn't noted in the CVSweb interface, so I assume the file is >>> stale. However, it was recently synced (today at ~noon) with portsnap. >> Does running 'portsnap extract textproc/libxml2' make the problem >> patch go away? > > Yes. Is this an issue with the `update' logic? I suppose that it's possible that there's a bug in the 'portsnap update' logic, but usually problems like this occur as a result of someone trying to use both portsnap and cvsup/csup. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid