This one is likely already fixed.

We build rpm-ostree with the json-c provided on the repositories. It looks like we have been using `json-c-0.13.1-3` for a while.

We can see we are shipping rpm-ostree built with `json-c-0.13.1-3` on CentOS 8 even since 2022.2.8.gd50a74bd:

https://koji.mbox.centos.org/pkgs/packages/rpm-ostree/2022.2.8.gd50a74bd/2.el8/data/logs/x86_64/root.log

 

On the current RHCOS build we are still looking good:

bash-4.4# rpm-ostree --version
rpm-ostree:
 Version: '2022.10'
 Git: 6b302116c969397fd71899e3b9bb3b8c100d1af9
 Features:
  - rust
  - compose
  - rhsm

 

bash-4.4# rpm -qa rpm-ostree
rpm-ostree-2022.10.86.gd8f0c67a-3.el8.x86_64

bash-4.4# rpm -qa json-c
json-c-0.13.1-3.el8.x86_64

 

bash-4.4# ldd -v /usr/bin/rpm-ostree | grep libjson
    libjson-glib-1.0.so.0 => /lib64/libjson-glib-1.0.so.0 (0x00007f8d369cc000)
    libjson-c.so.4 => /lib64/libjson-c.so.4 (0x00007f8d34cf1000)
        libjson-c.so.4 (JSONC_0.14) => /lib64/libjson-c.so.4
    /lib64/libjson-glib-1.0.so.0:
    /lib64/libjson-c.so.4:

 

bash-4.4# rpm -q --whatprovides /lib64/libjson-c.so.4
json-c-0.13.1-3.el8.x86_64