SSSD / ding-libs

#1908 libini_config kept the same libtool version even though the API changed
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Even though the libini_config API was changed substantially in the 1.0 release, the -version parameter was the same (3.0.0). We should bump the version to allow packaging tools such as RPMs to detect that the SSSD (or other consumers) were built with an incompatible version.

Fields changed

owner: somebody => okos
patch: 0 => 1
status: new => assigned

The change itself was OK, just the title of the ticket was wrong which caused all the confusion.

summary: libini_config kept the same SONAME even though the API changed => libini_config kept the same libtool version even though the API changed

Fields changed

milestone: NEEDS_TRIAGE => Tools 1.0.1
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to okos
- Issue set to the milestone: Tools 1.0.1
Metadata
None
None
None
Normal
defect
INI Parser
1.9.5
0
1
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.