Re: Unannounced .so version bump in gtest 1.13.0

[Ben Beasley]

I finished checking for fallout from the gtest 1.13.0 update in Rawhide.
The following packages built with GCC 13 but FTBFS with gtest-0.13.0 and 
have NOT been patched yet:

abseil-cpp (https://bugzilla.redhat.com/show_bug.cgi?id=2164154); this 
one is a nontrivial regression that has been reported upstream
deepin-calculator (https://bugzilla.redhat.com/show_bug.cgi?id=2164921)
deepin-network-utils (https://bugzilla.redhat.com/show_bug.cgi?id=2164920)
dtkcore (https://bugzilla.redhat.com/show_bug.cgi?id=2164924)
dtkwidget (https://bugzilla.redhat.com/show_bug.cgi?id=2164925)
gstreamermm (https://bugzilla.redhat.com/show_bug.cgi?id=2165230)

The following started to FTBFS with GCC 13 and have not yet been 
patched, so it’s unclear whether or not they have any issues with 
gtest-0.13.0:

android-tools (https://bugzilla.redhat.com/show_bug.cgi?id=2164598)
fcitx5-mozc (https://src.fedoraproject.org/rpms/fcitx5-mozc/pull-request/1)
folly (https://bugzilla.redhat.com/show_bug.cgi?id=2165219)

Same as above, but something else triggered the FTBFS:

mkvtoolnix (Ruby 3.2: https://bugzilla.redhat.com/show_bug.cgi?id=2161534)
root (numpy 1.24.1: https://github.com/root-project/root/issues/12148)
sdformat (Ruby 3.2: https://bugzilla.redhat.com/show_bug.cgi?id=2165939)

The following appear to be OK with gtest-0.13.0, or they have already 
been patched for gtest-0.13.0 (in the rawhide branch or in an open PR). 
A *large* minority of these did need to be patched for gtest-0.13.0 or 
for GCC 13.

ImageMagick
InsightToolkit
Macaulay2
PDAL2
apitrace
apt
arbor
assimp
barrier
bear
binaryen
bloaty
cachelib
cantera
casc
cctz
ceph
colobot
cpp-httplib
cpp-jwt
davix
ddnet
deepin-control-center
deepin-dock
deepin-editor
deepin-launcher
deepin-qt5integration
deepin-session-shell
deepin-session-ui
deepin-system-monitor
deepin-terminal
dosbox-staging
dtkgui
dwgrep
easyloggingpp
elements
fbthrift
fizz
flann
fbthrift
gazebo
gfal2
gnome-commander
gnucash
google-benchmark
google-cpu_features
gplugin
guidelines-support-library
gumbo-parser
highway
jd
jpegxl
jsonnet
lib3mf
libcamera
libecpint
libindi
libkiwix
libkml
libphonenumber
librime
libyuv
litehtml
luminance-hdr
mathic
mathicgb
mcrouter
memtailor
mir
moveit
msgpack
nativejit
ninja-build
nvtop
oomd
openclonk
opentype-sanitizer
partio
pcl
petpvc
phd2
proj
proxygen
prusa-slicer
python-html5-parser
python-steps
rapidjson
rapidyaml
rlottie
rnp
sdformat
sdsl-lite
seqan3
sipp
snappy
sonivox
sqlitecpp
srt
strawberry
synergy
uriparser
uvw
wabt
wangle
watchman
wdt
wlcs
xtensor
xtensor-python
zimlib
zstd

>  On Jan 24, 2023, at 11:58 AM, Ben Beasley
> <code(a)musicinmybrain.net&gt; wrote:
>
>  The recent update of gtest to 1.13.0 in Rawhide bumped the .so 
>  version. I reminded the maintainers of the Updates Policy for Rawhide 
>  and asked them to please announce and coordinate similar updates in 
>  the future[1].
>
>  The following packages depend on a specific .so version of gtest/gmock 
>  at runtime and already have FTI bugs: ceph, davix, gfal2, libcamera, 
>  mir, python-steps, and wlcs.
>
>  The list of packages that BuildRequire gtest/gmock is huge. I haven’t 
>  attempted to determine the full last of packages that could be 
>  impacted, or to explicitly (B)CC their maintainers on this message.
>
>  There is a higher than usual chance that packages that simply 
>  BuildRequire gtest/gmock will FTBFS, because gtest 1.13.0 drops 
>  support for C++ standard versions older than C++14. In *most* cases 
>  where a package’s build system enforces a specific older C++ version 
>  like C++11, it should be OK to patch that out and build with the 
>  compiler’s default C++ standard, or, more conservatively, enforce 
>  C++14 instead of C++11.
>
>  [1] https://bugzilla.redhat.com/show_bug.cgi?id=2161870#c3
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam, report it: 
>  https://pagure.io/fedora-infrastructure/new_issue