wrowe
commented
2 years ago Repository and docs resolved, maintainership not resolved.
Closed wrowe closed 2 years ago
wrowe
commented
2 years ago Repository and docs resolved, maintainership not resolved.
wrowe
commented
2 years ago Maintainership of libxml2 has been accomplished for the time being, closing as resolved
https://gitlab.gnome.org/GNOME/libxml2/-/commit/343bf0d39bf661ac5a3ae2e9251f489c5d1eb471
libxml2 seems to be going through problematic transitions;
https://gitlab.gnome.org/GNOME/libxml2 is the new canonical home of the project, the xmlsoft.org site seems to be deprecated, and that ftp site seems to be down. If this were not the case, the site and downloads at xmlsoft.org are still transmitted in the clear and trivially subject to MITM manipulation. No crypto-strength hashes or gpg signatures are published from a secure site, so these can't be consumed under any responsible organization's security posture.
In the transition to gitlab, github became a mirror, but https://github.com/GNOME/libxml2/releases was purged of all prior release source tarballs.
Release tarballs had the additional step of running autotools against the tagged source tree to generate configure scripts for unix. Obtaining the available source repository image from either gitlab or github will require the Makefile.preconfig step to be performed on the downloaded release tarball, a step that previously could be avoided when gathering, download, and building release on unix (but not when building bleed, snapshot, etc). This must be updated in the README etc.
https://gitlab.gnome.org/GNOME/libxml2/-/issues/319 further indicates that there are no active maintainers, it may prove necessary to drop support for mod_proxy_html and rely exclusively on the expat library, if the libxml2/libxslt situation does not improve.