textproc/libxml2 and failed patching after using portsnap...

Garrett Cooper yanefbsd at gmail.com
Sat Jan 17 14:34:20 PST 2009


On Sat, Jan 17, 2009 at 1:49 PM, Garrett Cooper <yanefbsd at 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


More information about the freebsd-ports mailing list