bump(main/libxml2): 2.15.0 - #26748
Conversation
|
Finished the rebuild testing.
Previous error
Looks like a double prefix error. CMake Error in src/modules/rubberband/CMakeLists.txt:
Imported target "PkgConfig::rubberband" includes non-existent path
"/data/data/com.termux/files/usr/data/data/com.termux/files/usr/include"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
* The path was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and references files it does not
provide.
|
|
|
I got |
That compiler error was fixed in this upstream commit lsh123/xmlsec@ef0e3b5. It will be added to xmlsec 1.3.8 release. |
|
I'll make a backport patch and rip out my non-fix fix. |
|
The problem with webkit2gtk-4.1 and webkitgtk-6.0 is that they have |
|
Okay so that isn't Libxml2 related then, right? |
|
Correct, however if |
|
That only leaves |
|
- Remove `libxml2-python-static` subpackage (empty) - Update project homepage (previous is a redirect) - Use Meson build system - Enable ICU support - Enable history and readline support for `xmllint` - Cleanup assorted jank
|
Patching out doxygen from the doc/meson.build was pretty easy, so we don't need to add it to the build container. |
|
All tests I've done on the reverse dependencies for Libxml2 have come up fine,so this should be good to merge. |
This took me the better part of a day since it just turned into one thing after the other.
To quickly summarize the things I ran into without inducing madness in the reader:
(Put a pin in that...)
libxml2doxygen, alright... Meson it is then.Had to get that working by overwriting
termux_step_configure()but that worked without issues.xmllint's shell mode.libxml2-python-staticis empty now.I checked the Arch package, that's just how it is now.
There is no more
gtk-doc, but a shit ton ofhtmlones.xmlcatalog.1andxmllint.1manpages are ending up inmaninstead ofman/man1This seems like an error in the
CMakeLists.txt.(Put a pin in that...)
https://gitlab.gnome.org/GNOME/libxml2/-/blob/2.15/CMakeLists.txt?ref_type=heads#L570-580
So, that pin from earlier.
@Biswa96 pointed me at this.
https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398
It looks like Libxml2 is effectively without an upstream maintainer at this time, which partially explains some of the jank I encountered this update cycle.
I also had a look at the Meson summary and tried enabling
It builds with those but throws some compiler warnings.