Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: groenveld@acm.org (John D Groenveld)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: pkg/ports, pkg audit, and libxml2
Date: 16 Jun 2025 16:55:54 GMT
Organization: Groenveld.US
Lines: 25
Message-ID: <mbb0kqFdrolU1@mid.individual.net>
References: <ydwm9evsy6.fsf@UBEblock.psr.com> <slrn10504te.1p7b.naddy@lorvorc.mips.inka.de>
X-Trace: individual.net LUnmJ7boSCoaxMxMuNx+hgvj9/fMWPUsFRn7TQpNAwfc9e6aCC
Cancel-Lock: sha1:UcEHrqFwnZ5N+6YjfJMK96oqjm8= sha256:RkW+bfMTNOSEjbsq6uDIkNdwq5af5b5J6I7lvEWLS7g=

In article <slrn10504te.1p7b.naddy@lorvorc.mips.inka.de>,
Christian Weisgerber  <naddy@mips.inka.de> wrote:
>Yes, that is unusually long and... *checks repository*... the port
>still hasn't been updated.

main is till 2.11.9:
<URL:https://cgit.freebsd.org/ports/plain/textproc/libxml2/Makefile>

>I _suspect_ the problem is that the port is still at 2.11.x, libxml
>head is at 2.14.x, and there are breaking changes inbetween that
>need to be dealt with. 

Unfortunately.
<URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279705>

>(OpenBSD went from 2.13.x to 2.14.x in April
>and had to deal with some breakage.)

Looks like there's Porters activity fixing breakage and deprecating
ports that are dependent on the legacy API but no longerm maintained
by upstream:
<URL:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=Open&bug_status=UNCONFIRMED&bug_status=New&bug_status=In%20Progress&field0-0-0=product&field0-0-1=component&field0-0-2=alias&field0-0-3=short_desc&field0-0-4=status_whiteboard&no_redirect=1&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced&type0-0-0=substring&type0-0-1=substring&type0-0-2=substring&type0-0-3=substring&type0-0-4=substring&value0-0-0=libxml2&value0-0-1=libxml2&value0-0-2=libxml2&value0-0-3=libxml2&value0-0-4=libxml2>

John
groenveld@acm.org