Hi all,

In Ubuntu 26.04, our libglapi-amber package only provides
libglapi.so.0.0.0, and is also now the only provider of that file in
the distro, from a search via `apt-file find
/usr/lib/x86_64-linux-gnu/libglapi.so.0.0.0`. (Previously,
libglapi-mesa also provided it, hence our libglapi-amber declaring a
conflict with our libglapi-mesa package).

However, with libglapi.so.0.0.0 no longer being provided by
libglapi-mesa in 26.04, I am evaluating whether there is still any
legitimate reason for libglapi-amber to conflict with libglapi-mesa. I
ran a script that does the following to see if any other ELF files in
any other binary packages in Ubuntu export the same symbols as
libglapi.so.0.0.0:
1. Aggregate all defined symbols from `nm -D --defined-only libglapi.so.0.0.0`
2. Search https://codesearch.debian.net/ for each symbol
3. For each source package found in (2), download all binary packages
produced by that source package in Ubuntu 26.04
4. Run `nm -D --defined-only <ELF file>` for each ELF file in each
binary package
5. Flag any other packages/files that export any of the same symbols in (1)

This did not return any matches, but before I propose removing the
conflict relationship in Resolute and allowing libglapi-amber and
libglapi-mesa to be coinstallable, I'd like upstream's opinion on
whether I'm missing anything important here. (I realize Debian
codesearch may not be a 1:1 match with Ubuntu Resolute for our results
of interest, and am trying to find an equivalent way to do that part
of the search on Ubuntu.)

Thanks,
-- 
Mitchell Augustin
Software Engineer - Ubuntu Partner Engineering
Email:[email protected]
[email protected]
Location:United States of America (Central Time)


canonical.com
ubuntu.com

Reply via email to