On Tuesday, December 9, 2025 8:18:13 PM Mountain Standard Time Seyed Mohamad Amin Modaresi wrote: > Hi Soren. > > Our source is libgxml version 0.20.4 > And soname of so files is 2.0.2 > > Because of these binary name is 0.20-2.0.2 > > See https://udd.debian.org/lintian-tag/package-name-doesnt-match-sonames > > Out put of following command is 2.0.2: > > objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n > -e's/^[[:space:]]*SONAME[[:space:]]*//p' | \ sed -r -e's/([0-9])\.so\./\1-/; > s/\.so(\.|$)//; y/_/-/; s/(.*)/\L&/'
Usually only the major versio of the SONAME is used in the package names. Using the full triplet is very rare. It would mean that a breaking change was introduced in the library between 2.0.0 and 2.0.2. Is that really the case (third digit changes, by definition, are not supposed to introduce big changes)? Or is this an instance of upstream being sloppy and listing the full triplet in the SONAME where they should just list the first digit? This causes unneeded problems for Debian because it means that every update would need to go through NEW (every time a package name changes). The upstream name for the main package is gxml, not libgxml. In these cases, typically we would name the source package gxml to match. Source: libgxml-0.20 -> gxml Package: libgxml-doc -> gxml-doc I assume you saw the comments on the email I sent to the mailing lists. We should follow the instructions at: https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/debian/ latest/debian/policy.txt?ref_type=heads https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/debian/ latest/debian/gobject-introspection.README.Debian Particularly by Build-Depending on dh-sequence-gir (which automates dh_girepository and ${gir:Depends} and ${gir:Provides}). -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
