Skip to content

[3.1] libapparmor: fix mistaken SO version bump

Steve Beattie requested to merge smb/apparmor:fix-3.1-so_version into apparmor-3.1

In commit 7c722400 ("Prepare for AppArmor 3.1 release"), as preperation for the AppArmor 3.1.0 release, the SO versioning information was adjusted, using a more significant bump to give prior AppArmor releases room to address bugs in libapparmor without ending up with conflicting SO versions. Unfortunately, that process was untested and because AA_LIB_AGE was not incremented by the same amount as AA_LIB_CURRENT, this resulted in an accidental major SO versions bump with the library SO version being:

libapparmor.so.4.9.0

This commit increments AA_LIB_AGE by the same amount, resulting in a library versioned as:

libapparmor.so.1.12.0

and adds a note to mention that AA_LIB_AGE needs to be incremented in the same way as AA_LIB_CURRENT. This fix is intended to address this for the 3.1 branch; I'd like to find a better approach for the development branch that can be used in future AppArmor primary releases.

In general, thanks to symbol versioning (see libraries/libapparmor/src/libapparmor.map) we should not need to ever bump the SO version except in an extreme case.

Fixes: 7c722400 ("Prepare for AppArmor 3.1 release") Signed-off-by: Steve Beattie steve.beattie@canonical.com Bug: #266 (closed)

Merge request reports