It is now provided by glibc. I think you can keep it as a compat symbol (i.e. a symbol without a default version).
I don't see that any glibc 2.25 builds have been done yet. Do you anticipate that 2.25 (or newer) will be pushed as an update for F25, or will it appear in F26? Can you point me to an example of how to declare a function as a compat symbol? Does this have to do with GCC's visibility attribute? Thanks! Eric
Created attachment 1246594 [details] explicit_bzero-compat.patch The attached patch should turn the symbol into a compat symbol. Before: [fweimer@oldenburg libbsd]$ eu-readelf --symbols=.dynsym ./src/.libs/libbsd.so | grep explicit_bzero 125: 0000000000004c30 39 FUNC GLOBAL DEFAULT 13 explicit_bzero@@LIBBSD_0.8 The “@@” indicates that this is a default version against which applications can link. After: [fweimer@oldenburg libbsd]$ eu-readelf --symbols=.dynsym ./src/.libs/libbsd.so | grep explicit_bzero 126: 0000000000004c30 39 FUNC GLOBAL DEFAULT 13 explicit_bzero The “@@” is gone, meaning that this is a compat symbol.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
It may be worth to remove /usr/share/man/man3/explicit_bzero.3.gz as well. It conflicts now with man-pages.
glibc 2.26 also introduces reallocarray, which should be turned into a compatibility symbol as well.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still not fixed in rawhide. This is rather disappointing.