We have received guidance (from Fesco, I believe) that we should not attempt to push any non-approved changes into Fedora 27. We have one pending update with a minimal ld.so fix which was accepted as a freeze exception:
https://bodhi.fedoraproject.org/updates/glibc-2.26-16.fc27
I think the best course of action for us is to avoid any updates to the f27 branch in dist-git for now, until the Fedora 27 release. After the release, we should immediately drop glibc-rh1506802.patch, sync with the upstream release branch (which includes this patch), and pick up the glob64 API fix we are currently missing.
Thanks, Florian
On 11/06/2017 01:04 PM, Florian Weimer wrote:
We have received guidance (from Fesco, I believe) that we should not attempt to push any non-approved changes into Fedora 27. We have one pending update with a minimal ld.so fix which was accepted as a freeze exception:
https://bodhi.fedoraproject.org/updates/glibc-2.26-16.fc27
I think the best course of action for us is to avoid any updates to the f27 branch in dist-git for now, until the Fedora 27 release. After the release, we should immediately drop glibc-rh1506802.patch, sync with the upstream release branch (which includes this patch), and pick up the glob64 API fix we are currently missing.
Agreed. That sounds like a good plan.