Date: Sat, 17 Jan 2009 14:34:18 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Colin Percival <cperciva@freebsd.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: textproc/libxml2 and failed patching after using portsnap... Message-ID: <7d6fde3d0901171434l6e766f8co350d6f02bab4281d@mail.gmail.com> In-Reply-To: <7d6fde3d0901171349o20f1b8d2x944bcae5394b8eb9@mail.gmail.com> References: <7d6fde3d0901171349o20f1b8d2x944bcae5394b8eb9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 17, 2009 at 1:49 PM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> Hello,
> This is just a notice that a patch is no longer needed with
> textproc/libxml2 -- it appears to have been checked in upstream:
>
> ===> Applying FreeBSD patches for libxml2-2.7.2_1
> Ignoring previously applied (or reversed) patch.
> 1 out of 1 hunks ignored--saving rejects to include/libxml/parser.h.rej
> 19 out of 24 hunks failed--saving rejects to parser.c.rej
> Ignoring previously applied (or reversed) patch.
> 1 out of 1 hunks ignored--saving rejects to parserInternals.c.rej
> => Patch patch-CVE-2008-3281 failed to apply cleanly.
> *** Error code 1
>
> 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.
> I've seen similar things in the past on a handful of occasions
> with portsnap (not csup) with stale files -- is this an infrastructure
> bug, just stale data that's going to get cycled out, or something
> else? The fix is trivial (delete the file) but it still is a bit of an
> annoyance.
> Thanks,
> -Garrett
I ran into more issues like this with x11-toolkits/gtk20 ;( (4
patches failed to apply cleanly)...
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0901171434l6e766f8co350d6f02bab4281d>