Hi Siddhesh,
On Tue, 29 Jul 2014 00:40:03 +0530
Siddhesh Poyarekar <siddhesh(a)redhat.com> wrote:
Hi,
I have updated glibc in rawhide to the latest master after verifying
that it works fine on x86 (32 and 64-bit). The build is in progress
here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=7204483
Please also test this against your architectures and report failures
if any. Dan, please let me know if the setuid failure you saw on
python persists and if it does, please let me know which machine I can
access to debug the issue.
we did glibc builds on s390 and ppc and they were successful
http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1447893
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1964230
We then tried to rebuild python2 with the new glibc and it works for
ppc64 and ppc64le, no test failures there. We see some random failures
on ppc64p7 (Power7 variant of ppc64), but we are still working on
confirming they are not transient and we can skip this variant if
needed.
For F21, the plan is to continue to track glibc upstream master till
it branches off to 2.20. This should happen some time in the middle
or end of August, so it ought to be well before Fedora turns beta.
I'm planning to track f21 much more slowly though, since I got
feedback that folks wanted slightly slower churn in f21. I'll
probably do something like rebasing rawhide in the beginning of the
week and then merging that point into f21 by the end of it. Please
let me know if anyone has preferences regarding this.
Can we get the glibc-2.19.90-31.fc22 build merged to f21 now as it
seems work in all required environments, so we can unblock the builds
depending on it?
Dan