[Bug 257143] textproc/py-libxml2: Fails to run: libxml2mod.so: Undefined symbol "xmlPopOutputCallbacks" (breaking textproc/itstool -> textproc/gtk-doc / textproc/yelp-xsl

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 13 Jul 2021 05:53:48 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257143

Kubilay Kocak <koobs_at_FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Open                        |Closed
              Flags|maintainer-feedback?(gnome_at_ |
                   |FreeBSD.org),               |
                   |maintainer-feedback?(deskto |
                   |p_at_FreeBSD.org),             |
                   |maintainer-feedback?(kwm_at_Fr |
                   |eeBSD.org),                 |
                   |merge-quarterly?            |
           Assignee|desktop_at_FreeBSD.org         |koobs_at_FreeBSD.org
         Resolution|---                         |Not A Bug
                 CC|                            |arrowd_at_FreeBSD.org

--- Comment #7 from Kubilay Kocak <koobs_at_FreeBSD.org> ---
(In reply to Chris Hutchinson from comment #6)

Unless the symbols in question are only provided in 2.9.10_3, and the ports
require those symbols, then yes. 

However, this appears to be the likely result of a libxml2 shared library ABI
change, without a subsequent py-libxml2 (consumer) shared library update.

That can be caused by shared library version changes, without consumer ports
having their PORTREVISION bumped, or by modifying port options that change the
shared (libxml2) library ABI, without rebuilding consumer ports (py-libxml2) 

The last update to libxml2 was 21 Jun 2021 21:19:10, cc'ing maintainer in case
they're aware of possible consumer ports impacts for additional comment, but
this appears to be 'not a bug'.

Accordingly, closing as resolved given comment 6.

Don't hesitate to re-open the issue with additional detail and reproduction
steps if that is not the case, or additional changes are required

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tue Jul 13 2021 - 05:53:48 UTC

Original text of this message