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

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

Fields changed

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

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

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

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

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

Fields changed

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

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to okos
- Issue set to the milestone: Tools 1.0.1

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2950

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata