Date: Sat, 17 Jan 2009 17:51:12 -0800 From: Colin Percival <cperciva@freebsd.org> To: Garrett Cooper <yanefbsd@gmail.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: textproc/libxml2 and failed patching after using portsnap... Message-ID: <49728B10.4080808@freebsd.org> In-Reply-To: <7d6fde3d0901171557v4e2d6e9enc564c8bdab100931@mail.gmail.com> References: <7d6fde3d0901171349o20f1b8d2x944bcae5394b8eb9@mail.gmail.com> <49725E61.6070701@freebsd.org> <7d6fde3d0901171557v4e2d6e9enc564c8bdab100931@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: > On Sat, Jan 17, 2009 at 2:40 PM, Colin Percival <cperciva@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49728B10.4080808>