Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • L libxml2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 98
    • Issues 98
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • libxml2
  • Issues
  • #433
Closed
Open
Issue created Nov 03, 2022 by Adam Williamson@adamw

2.10 changes ABI without warning

It seems like a lot of change and cleanup and removals have gone into libxml 2.10. We noticed downstream that, built with the same options as 2.9.14, 111 symbols were removed from libxml2.so.2 without the soname changing. This broke quite a lot of dependent applications.

This doesn't seem like appropriate library maintenance? Symbols should not disappear without an soname change like this.

We figured out that building with --with-legacy --with-ftp --with-xptr-locs should probably bring back the important ones, leaving only the removals from 4a8c71eb and fe9f76eb , which probably shouldn't cause problems in practice. But still, it kinda feels like an soname bump should have happened here.

Assignee
Assign to
Time tracking