gnome-desktop3 was updated a week ago to 3.27.90, which bumped ABI from .so.12 to .so.17. AFAICS no notice was given, nor am I sure that this was even noticed by the maintainer, because once again:
%{_libdir}/lib*.so.*
I have rebuilt my affected package.
On Sun, Feb 18, 2018 at 1:13 PM, Yaakov Selkowitz yselkowi@redhat.com wrote:
gnome-desktop3 was updated a week ago to 3.27.90, which bumped ABI from .so.12 to .so.17. AFAICS no notice was given, nor am I sure that this was even noticed by the maintainer, because once again:
%{_libdir}/lib*.so.*
I have rebuilt my affected package.
The wildcard in the files list is particularly dangerous because GNOME packages are updated by a script; humans only look when there are build failures. And unlike most other GNOME libraries, gnome-desktop does not pretend to have a stable API.
I've junt changed it to:
%{_libdir}/libgnome-desktop-3.so.17*
Belatedly, I realize that will break if the soname is ever bumped to 170. What is considered the best practice for this?
Michael
On Sun, Feb 18, 2018 at 10:10 PM, mcatanzaro@gnome.org wrote:
On Sun, Feb 18, 2018 at 1:13 PM, Yaakov Selkowitz yselkowi@redhat.com wrote:
gnome-desktop3 was updated a week ago to 3.27.90, which bumped ABI from .so.12 to .so.17. AFAICS no notice was given, nor am I sure that this was even noticed by the maintainer, because once again:
%{_libdir}/lib*.so.*
I have rebuilt my affected package.
The wildcard in the files list is particularly dangerous because GNOME packages are updated by a script; humans only look when there are build failures. And unlike most other GNOME libraries, gnome-desktop does not pretend to have a stable API.
I've junt changed it to:
%{_libdir}/libgnome-desktop-3.so.17*
Belatedly, I realize that will break if the soname is ever bumped to 170. What is considered the best practice for this?
I usually use something like the following:
%global somajor 17 ... %{_libdir}/libgnome-desktop-3.so.%{somajor}{,.*}
-
mcatanzaro＠gnome.org -
Neal Gompa -
Yaakov Selkowitz