glibc 2.19 introduced _DEFAULT_SOURCE feature macro which should replace _BSD_SOURCE and _SVID_SOURCE feature macros. glibc 2.20 will emit warning if the old are macros are used. See <https://sourceware.org/glibc/wiki/Release/2.20#Packaging_Changes>. This already happens in F21 as there is glibc-2.19.90, a 2.20 prerelease. The point of man-pages is that various function synopses still promote _BSD_SOURCE and _SVID_SOURCE instead of the _DEFAULT_SOURCE. E.g.: NAME mkstemp, mkostemp, mkstemps, mkostemps - create a unique temporary file SYNOPSIS #include <stdlib.h> int mkstemp(char *template); int mkostemp(char *template, int flags); int mkstemps(char *template, int suffixlen); int mkostemps(char *template, int suffixlen, int flags); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): mkstemp(): _BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED || /* Since glibc 2.12: */ _POSIX_C_SOURCE >= 200112L It's necessary to update each manual pages referring to the _BSD_SOURCE or _SVID_SOURCE to recommend _DEFAULT_SOURCE instead.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Upstream maintainer here. Yup, known problem. 190 pages to fix. I'll get to it at some point. Help welcome (in the meantime, see http://man7.org/linux/man-pages/man7/feature_test_macros.7.html).
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Note that this problem will be fixed in the upcoming upstream release, man-pages-4.05, which will be released in the next few weeks.
Hooray!
Thanks Michael, I'll backport the changes to F22 and F23.
(In reply to Nikola Forró from comment #7) > Thanks Michael, > > I'll backport the changes to F22 and F23. Hmmm -- that may be more of a task than you expect. If you do attempt it, I'd be interested to hear how it goes.
(In reply to Michael Kerrisk from comment #8) > (In reply to Nikola Forró from comment #7) > > Thanks Michael, > > > > I'll backport the changes to F22 and F23. > > Hmmm -- that may be more of a task than you expect. If you do attempt it, > I'd be interested to hear how it goes. Ohh - I realize I may have misunderstood what you meant by backport. Maybe you just mean to release man-pages-4.05 to F22 and F23. That's simple, of course.
(In reply to Michael Kerrisk from comment #9) > Ohh - I realize I may have misunderstood what you meant by backport. Maybe > you just mean to release man-pages-4.05 to F22 and F23. That's simple, of > course. No, I really did mean backport. But you are right, that's not going to be easy. Maybe I'll have to reconsider it.
(In reply to Nikola Forró from comment #10) > (In reply to Michael Kerrisk from comment #9) > > Ohh - I realize I may have misunderstood what you meant by backport. Maybe > > you just mean to release man-pages-4.05 to F22 and F23. That's simple, of > > course. > No, I really did mean backport. But you are right, that's not going to be > easy. Maybe I'll have to reconsider it. In general, there's no reason to ever do such things. man-pages crefully maintains information about historical versions of the kernel and libc. By all means, backport (any) future version of man-pages to an older Fedora release. But backporting individual patches provides no benefit, only work.
Commits: f22: http://pkgs.fedoraproject.org/cgit/rpms/man-pages.git/commit/?h=f22&id=4a43dfe3553c3dc1b642cb03fd189f53cc012c2a f23: http://pkgs.fedoraproject.org/cgit/rpms/man-pages.git/commit/?h=f23&id=54496c135254a5211b4717be0ac302fe6a61f06f f24: http://pkgs.fedoraproject.org/cgit/rpms/man-pages.git/commit/?h=f24&id=8b6bf23b929064052bfc16141553f83167e5ed92
man-pages-4.04-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ae41a172c4
man-pages-4.00-7.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7de4dea1ac
man-pages-3.81-5.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-2bab047f46
man-pages-4.04-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ae41a172c4
man-pages-3.81-5.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2bab047f46
man-pages-4.00-7.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7de4dea1ac
man-pages-4.04-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
man-pages-4.00-7.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
man-pages-3.81-5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.