fweimer reported a new issue against the project: `releng` that you are following: `` Please check the impact of the [proposed change](https://fedoraproject.org/wiki/Changes/GLIBC230). ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
mohanboddu added a new comment to an issue you are following: `` @fweimer RelEng acks the change and we will include it in as part of F31 mass rebuild and we will keep the communication open for any changes that needs to be done. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
mohanboddu added a new comment to an issue you are following: `` @fweimer Status Check: Next Tue, that is July 23rd 2019 is F31 mass rebuild. Please make sure everything is ready for it.
Please let us know if there is something blocking your change in advance.
Thanks ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
fweimer added a new comment to an issue you are following: `` We are not yet ready. We are affected by what appears to be a [kernel-headers bug](https://bugzilla.redhat.com/show_bug.cgi?id=1731262).
Unfortunately, we had some process issues on the glibc side, too, and therefore I cannot say with confidence that we are good once the buildroot is fixed. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
mohanboddu added a new comment to an issue you are following: `` @fweimer So, do you have any estimate when it will be fixed? And do you want it to take it to FESCo for change in mass rebuild date? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
fweimer added a new comment to an issue you are following: `` The kernel-headers bug has been fixed. I have asked whether glibc is ready, and I have received some positive feedback. However, `rev /etc/passwd` is still broken. I think this is actually a `util-linux` bug, distinct from [swbz#24677](https://sourceware.org/bugzilla/show_bug.cgi?id=24677).
I hope to have some clarity within about 14 hours. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
fweimer added a new comment to an issue you are following: `` My proper upstream patch was not reviewed and ack'ed in time.
I'm in the processes of backing out the offending upstream commit in rawhide. See [#1732406](https://bugzilla.redhat.com/show_bug.cgi?id=1732406). ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
mohanboddu added a new comment to an issue you are following: `` @fweimer Thanks for the update, we will use `glibc-2.29.9000-34.fc31` for mass rebuild. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
bcotton added a new comment to an issue you are following: `` @fweimer does this mean the glibc 2.30 change will be deferred to F32 (or canceled in favor of the next glibc release)? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
ignatenkobrain added a new comment to an issue you are following: `` @bcotton, I think that means that @fweimer just reverted offending commit instead of applying his fix. Basically 2.29.9000 is pre-2.30, so I think it will be included.
Florian, correct me if I'm wrong. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
bcotton added a new comment to an issue you are following: `` @ignatenkobrain ah! I missed the '9000' part and just focused on the '2.29'. Thanks ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8462
rel-eng@lists.fedoraproject.org
-
Ben Cotton -
Florian Weimer
-
Igor Gnatenko
-
Mohan Boddu