# equery f =libavif-0.9.0-r2 * Searching for libavif ... * Contents of media-libs/libavif-0.9.0-r2: ... /usr/lib64/libavif.so -> libavif.so.10 /usr/lib64/libavif.so.10 -> libavif.so.10.0.0 /usr/lib64/libavif.so.10.0.0 # equery f =libavif-0.9.2 * Searching for libavif ... * Contents of media-libs/libavif-0.9.2: ... /usr/lib64/libavif.so -> libavif.so.12 /usr/lib64/libavif.so.12 -> libavif.so.12.0.0 /usr/lib64/libavif.so.12.0.0 # equery f =libavif-0.9.3 * Searching for libavif ... * Contents of media-libs/libavif-0.9.3: ... /usr/lib64/libavif.so -> libavif.so.13 /usr/lib64/libavif.so.13 -> libavif.so.13.0.0 /usr/lib64/libavif.so.13.0.0
It is indeed necessary to rebuild apps using libavif almost after each libavif upgrade.
(In reply to Daniel Novomeský from comment #1) > It is indeed necessary to rebuild apps using libavif almost after each > libavif upgrade. Thanks, I'll do it now.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=99e6986a58807e3fee767ee8db4107cfd7fea3cc commit 99e6986a58807e3fee767ee8db4107cfd7fea3cc Author: Sam James <sam@gentoo.org> AuthorDate: 2021-11-07 22:54:25 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-11-07 23:07:46 +0000 media-libs/libavif: define subslot ((very) unstable ABI) Closes: https://bugs.gentoo.org/822336 Signed-off-by: Sam James <sam@gentoo.org> media-libs/libavif/{libavif-0.8.4.ebuild => libavif-0.8.4-r1.ebuild} | 3 ++- .../libavif/{libavif-0.9.0-r2.ebuild => libavif-0.9.0-r3.ebuild} | 3 ++- media-libs/libavif/{libavif-0.9.1.ebuild => libavif-0.9.1-r1.ebuild} | 3 ++- media-libs/libavif/{libavif-0.9.2.ebuild => libavif-0.9.2-r1.ebuild} | 3 ++- media-libs/libavif/{libavif-0.9.3.ebuild => libavif-0.9.3-r1.ebuild} | 3 ++- media-libs/libavif/libavif-9999.ebuild | 3 ++- 6 files changed, 12 insertions(+), 6 deletions(-)