This update for apparmor fixes the following issue:
{
"binaries": [
{
"apache2-mod_apparmor": "2.8.2-56.18.2",
"apparmor-docs": "2.8.2-56.18.2",
"apparmor-parser": "2.8.2-56.18.2",
"apparmor-profiles": "2.8.2-56.18.2",
"apparmor-utils": "2.8.2-56.18.2",
"libapparmor-devel": "2.8.2-56.18.2",
"libapparmor1": "2.8.2-56.18.2",
"libapparmor1-32bit": "2.8.2-56.18.2",
"pam_apparmor": "2.8.2-56.18.2",
"pam_apparmor-32bit": "2.8.2-56.18.2",
"perl-apparmor": "2.8.2-56.18.2"
}
]
}
{
"binaries": [
{
"apache2-mod_apparmor": "2.8.2-56.18.2",
"apparmor-docs": "2.8.2-56.18.2",
"apparmor-parser": "2.8.2-56.18.2",
"apparmor-profiles": "2.8.2-56.18.2",
"apparmor-utils": "2.8.2-56.18.2",
"libapparmor-devel": "2.8.2-56.18.2",
"libapparmor1": "2.8.2-56.18.2",
"libapparmor1-32bit": "2.8.2-56.18.2",
"pam_apparmor": "2.8.2-56.18.2",
"pam_apparmor-32bit": "2.8.2-56.18.2",
"perl-apparmor": "2.8.2-56.18.2"
}
]
}