On 17/04/18 21:21, Chris Lamb wrote: > Hi Emilio, > > Disclaimer: I'm not a shared library expert, let alone a shlibs > one! However, as I understand it, we need to look for: > > * A "libfooX" & "libfooX-udeb" pair … > > * That both ship a "libBar.so.X" > > * libfooX's shlibs control file does not contain a line starting > with "udeb: libBar X libfooX-udeb"... > > (At a first approximation anyway...)
Yes, but libfooX may be named differently (i.e. it's not always a s/-udeb$//), and there may be several non-udebs affected. So I'd approach this in this way (in pseudocode): for each shared library in the -udeb there is a deb package with that library, and its shlibs contains a udeb line for that shared lib That would match your libfoo1 and libfoo1-udeb, but also something like libpango1.0-udeb shipping shared libraries from libpango-1.0-0, libpangocairo-1.0-0, libpangoxft-1.0-0 and libpangoft2-1.0-0. In that case, each one of those debs needs a udeb: fine for the libraries that the udeb ships. Hope that's clear. If not, please let me know. Thanks, Emilio
