7:53 a.m.
We currently have an invalid IFUNC resolver in libgcc.a on POWER
(rhbz#1467526). glibc in rawhide recently started linking that into the
library and there are significant problems with that (rhbz#1467518).
I'll be on PTO next week, and it does not seem likely that this is going
to be resolved upstream before that. If upstream (both glibc GCC are
involved) don't come up with a solution, I'm not sure
If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
least the following packages right after that because they have a
GLIBC_2.26 symbol version dependency:
inn-2.6.1-6.fc27.src.rpm
remctl-3.13-4.fc27.src.rpm
sudo-1.8.20p2-1.fc27.src.rpm
tmux-2.5-1.fc27.src.rpm
unbound-1.6.4-1.fc27.src.rpm
xorg-x11-server-1.19.3-6.fc27.src.rpm
Besides the glibc downgrade, I'm not aware of anything else we could do
to get ready for the mass rebuild in time.
Thanks,
Florian
8:38 a.m.
On 07/07/2017 02:53 PM, Florian Weimer wrote:
Besides the glibc downgrade, I'm not aware of anything else we
could do
to get ready for the mass rebuild in time.
I discussed this with Carlos, and we came up with this:
On POWER, the transition to the float128 format for the long double type
did not happen upstream in time for the glibc 2.26 release. This
transition was the reasons why we requested the mass rebuild. If no
other reason for a mass rebuild has surfaced, then we should just skip
the mass rebuild for the Fedora 27 release.
My concern is that the mass rebuild will reveal a substantial number of
issues on POWER, and we'd have to look at each one individually to see
if it is the known IFUNC resolver breakage.
Thanks,
Florian
9:11 a.m.
On Fri, Jul 07, 2017 at 03:38:32PM +0200, Florian Weimer wrote:
On 07/07/2017 02:53 PM, Florian Weimer wrote:
> Besides the glibc downgrade, I'm not aware of anything else we could do
> to get ready for the mass rebuild in time.
I discussed this with Carlos, and we came up with this:
On POWER, the transition to the float128 format for the long double type
did not happen upstream in time for the glibc 2.26 release. This
transition was the reasons why we requested the mass rebuild.
If no other reason for a mass rebuild has surfaced, then we should
just skip the mass rebuild for the Fedora 27 release.
Hm,
https://pagure.io/releng/issue/6853 is about Go piggy-backing on
the "normal" mass rebuild.
My concern is that the mass rebuild will reveal a substantial number
of
issues on POWER, and we'd have to look at each one individually to see
if it is the known IFUNC resolver breakage.
Yeah, the schedule for F27 is very
tight, things will be hard.
Zbyszek
8:52 a.m.
On 07/07/2017 04:11 PM, Zbigniew Jędrzejewski-Szmek wrote:
> If no other reason for a mass rebuild has surfaced, then we
should
> just skip the mass rebuild for the Fedora 27 release.
Hm, https://pagure.io/releng/issue/6853 is about Go piggy-backing on
the "normal" mass rebuild
Thanks, but those changes are unlikely to be ready for the mass rebuild,
and a separate rebuild of Go packages will be needed. (And even Go 1.8
FTBFS on most architectures in rawhide.)
So it's just the s390x import which remains as the rationale for a mass
rebuild.
Florian
9:36 a.m.
On Fri, Jul 7, 2017 at 2:38 PM, Florian Weimer <fweimer(a)redhat.com> wrote:
On 07/07/2017 02:53 PM, Florian Weimer wrote:
> Besides the glibc downgrade, I'm not aware of anything else we could do
> to get ready for the mass rebuild in time.
I discussed this with Carlos, and we came up with this:
On POWER, the transition to the float128 format for the long double type
did not happen upstream in time for the glibc 2.26 release. This
transition was the reasons why we requested the mass rebuild. If no
other reason for a mass rebuild has surfaced, then we should just skip
the mass rebuild for the Fedora 27 release.
The import of s390x was one reason.
> My concern is that the mass rebuild will reveal a substantial number of
> issues on POWER, and we'd have to look at each one individually to see
> if it is the known IFUNC resolver breakage.
>
> Thanks,
> Florian
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
3:20 p.m.
On 07/07/2017 08:53 AM, Florian Weimer wrote:
We currently have an invalid IFUNC resolver in libgcc.a on POWER
(rhbz#1467526). glibc in rawhide recently started linking that into the
library and there are significant problems with that (rhbz#1467518).
I'll be on PTO next week, and it does not seem likely that this is going
to be resolved upstream before that. If upstream (both glibc GCC are
involved) don't come up with a solution, I'm not sure
If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
least the following packages right after that because they have a
GLIBC_2.26 symbol version dependency:
inn-2.6.1-6.fc27.src.rpm
remctl-3.13-4.fc27.src.rpm
sudo-1.8.20p2-1.fc27.src.rpm
tmux-2.5-1.fc27.src.rpm
unbound-1.6.4-1.fc27.src.rpm
xorg-x11-server-1.19.3-6.fc27.src.rpm
Besides the glibc downgrade, I'm not aware of anything else we could do
to get ready for the mass rebuild in time.
IBM has worked through a patch that will fix the libgcc issue:
https://sourceware.org/ml/libc-alpha/2017-06/msg01430.html
All we need to do now is:
* Get the gcc trunk patch into F27 gcc.
* Rebuild gcc and libgcc.
* Rebuild glibc.
And that should be everything we need to do before the mass rebuild
start on the 12th.
I'm reaching out to Jakub/Marek on the gcc side to get help with this.
--
Cheers,
Carlos.
11:37 p.m.
On 07/07/2017 04:20 PM, Carlos O'Donell wrote:
On 07/07/2017 08:53 AM, Florian Weimer wrote:
> We currently have an invalid IFUNC resolver in libgcc.a on POWER
> (rhbz#1467526). glibc in rawhide recently started linking that into the
> library and there are significant problems with that (rhbz#1467518).
>
> I'll be on PTO next week, and it does not seem likely that this is going
> to be resolved upstream before that. If upstream (both glibc GCC are
> involved) don't come up with a solution, I'm not sure
>
> If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
> least the following packages right after that because they have a
> GLIBC_2.26 symbol version dependency:
>
> inn-2.6.1-6.fc27.src.rpm
> remctl-3.13-4.fc27.src.rpm
> sudo-1.8.20p2-1.fc27.src.rpm
> tmux-2.5-1.fc27.src.rpm
> unbound-1.6.4-1.fc27.src.rpm
> xorg-x11-server-1.19.3-6.fc27.src.rpm
>
> Besides the glibc downgrade, I'm not aware of anything else we could do
> to get ready for the mass rebuild in time.
IBM has worked through a patch that will fix the libgcc issue:
https://sourceware.org/ml/libc-alpha/2017-06/msg01430.html
All we need to do now is:
* Get the gcc trunk patch into F27 gcc.
* Rebuild gcc and libgcc.
* Rebuild glibc.
And that should be everything we need to do before the mass rebuild
start on the 12th.
I'm reaching out to Jakub/Marek on the gcc side to get help with this.
Status update:
* Get the gcc trunk patch into F27 gcc.
* Patch committed to trunk [Done -- IBM]
* Rebuild gcc and libgcc [In progress -- Red Hat]
* Blocked on several header issues and changes which make gcc FTBS.
Working on fixing the issues.
* Fedora backport [Not started]
* Rebuild gcc and libgcc [Not started]
* Rebuild glibc
* Patch committed to trunk [In progress -- IBM]
* Second round review complete, and final patch in progress.
* Sync to Fedora [Waiting -- Red Hat]
* Rebuild [Waiting -- Red Hat]
If we're lucky we can get everything ready for the 12th, but we might
need another day or two given how long it takes to build gcc on all
the arches.
--
Cheers,
Carlos.
1:59 a.m.
On 11 July 2017 at 05:37, Carlos O'Donell <carlos(a)redhat.com> wrote:
If we're lucky we can get everything ready for the 12th, but we
might
need another day or two given how long it takes to build gcc on all
the arches.
From someone sitting on the sidelines: Thanks for doing this
unglamorous work, lots of people appreciate it!
Richard
8:48 p.m.
On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
If we're lucky we can get everything ready for the 12th, but we
might
need another day or two given how long it takes to build gcc on all
the arches.
We are getting more luck. We'll see how tomorrow goes.
Status update:
* Get the gcc trunk patch into F27 gcc.
* Patch committed to trunk [Done -- IBM]
* Fedora backport [Done -- Red Hat]
* Rebuilds of glibc to fix gcc header issues [Done -- fweimer]
* Rebuild gcc and libgcc [In progress -- jakub]
https://koji.fedoraproject.org/koji/taskinfo?taskID=20462687
* Rebuild glibc
* Patch committed to trunk [In progress -- IBM]
* codonell talking to IBM about fix for static linking.
* Sync to Fedora [Waiting -- Red Hat]
* Waiting for new compiler to retest glibc builds.
* Rebuild [Waiting -- Red Hat]
* Fix Go 1.8.1 for s390x
* Recent patches get us to everything but s390x working:
golang 1.8.1: https://koji.fedoraproject.org/koji/taskinfo?taskID=20461040
golang 1.9: https://koji.fedoraproject.org/koji/taskinfo?taskID=20457700
Note: ppc64le are just testsuite issues.
* Fix s390x breakage [In progress -- jcajka]
--
Cheers,
Carlos.
2:34 a.m.
On Tue, 11 Jul 2017 21:48:46 -0400
Carlos O'Donell <carlos(a)redhat.com> wrote:
On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
> If we're lucky we can get everything ready for the 12th, but we
> might need another day or two given how long it takes to build gcc
> on all the arches.
We are getting more luck. We'll see how tomorrow goes.
Status update:
* Get the gcc trunk patch into F27 gcc.
* Patch committed to trunk [Done -- IBM]
* Fedora backport [Done -- Red Hat]
* Rebuilds of glibc to fix gcc header issues [Done -- fweimer]
* Rebuild gcc and libgcc [In progress -- jakub]
https://koji.fedoraproject.org/koji/taskinfo?taskID=20462687
* Rebuild glibc
* Patch committed to trunk [In progress -- IBM]
* codonell talking to IBM about fix for static linking.
* Sync to Fedora [Waiting -- Red Hat]
* Waiting for new compiler to retest glibc builds.
* Rebuild [Waiting -- Red Hat]
* Fix Go 1.8.1 for s390x
this is https://bugzilla.redhat.com/show_bug.cgi?id=1460254 -
buggy interaction between golang and new binutils
* Recent patches get us to everything but s390x working:
golang 1.8.1:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20461040 golang
1.9: https://koji.fedoraproject.org/koji/taskinfo?taskID=20457700
Note: ppc64le are just testsuite issues.
* Fix s390x breakage [In progress -- jcajka]
Dan
2:38 p.m.
On 07/12/2017 03:34 AM, Dan Horák wrote:
> * Fix Go 1.8.1 for s390x
this is https://bugzilla.redhat.com/show_bug.cgi?id=1460254 -
buggy interaction between golang and new binutils
That's right, we knew what it was, but fixing it is not that
easy since it's generic binutils machinery that should be
working correctly.
--
Cheers,
Carlos.
3:44 a.m.
On 07/12/2017 03:48 AM, Carlos O'Donell wrote:
* Rebuild glibc
* Patch committed to trunk [In progress -- IBM]
* codonell talking to IBM about fix for static linking.
Not needed for the mass rebuild IMHO.
* Sync to Fedora [Waiting -- Red Hat]
* Waiting for new compiler to retest glibc builds.
Current glibc master does not build in rawhide anymore:
malloc.c: In function 'tcache_init.part.9':
malloc.c:1590:50: error: array subscript is above array bounds
[-Werror=array-bounds]
#define fastbin(ar_ptr, idx) ((ar_ptr)->fastbinsY[idx])
~~~~~~~~~~~~~~~~~~~~^~~~~~
malloc.c:3572:26: note: in expansion of macro 'fastbin'
mfastbinptr *fb = &fastbin (av, idx);
^~~~~~~
It's probably triggered by constant propagation of the size parameter
into _int_malloc, but we'd have to look at GIMPLE dumps to be sure.
I think I'm going to commit my upstream sync to dist-git anyway because
it contains other adjustments for the upstream sync.
Thanks,
Florian
6:33 a.m.
On 07/12/2017 10:44 AM, Florian Weimer wrote:
On 07/12/2017 03:48 AM, Carlos O'Donell wrote:
> * Rebuild glibc
>
> * Patch committed to trunk [In progress -- IBM]
> * codonell talking to IBM about fix for static linking.
Not needed for the mass rebuild IMHO.
I was wrong about that. sln and ldconfig are affected by this issue, so
we need to fix it before the mass rebuild.
Thanks,
Florian
7:10 p.m.
On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
> If we're lucky we can get everything ready for the 12th, but we might
> need another day or two given how long it takes to build gcc on all
> the arches.
We are getting more luck. We'll see how tomorrow goes.
ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
the final golang rebuild with a fixed glibc (ppc64le failures fixed).
Less lucky and more lucky. The 32-bit ARM bug was solved overnight after
I pinged Nick Clifton. Which is *awesome* otherwise I'd be stuck
debugging 32-bit ARM code. All that is left is to wait for glibc final
builds to finish and rebuild Go 1.9.0, then we're ready for the mass rebuild.
Status update:
* Get the gcc trunk patch into F27 gcc. [Done]
* Patch committed to trunk [Done -- IBM]
* Fedora backport [Done -- Red Hat]
* Rebuilds of glibc to fix gcc header issues [Done -- fweimer]
* Rebuild gcc and libgcc [Done -- jakub]
https://koji.fedoraproject.org/koji/taskinfo?taskID=20462687
* Rebuild glibc
* Patch committed to trunk [Done -- IBM]
* Sync to Fedora [Done -- Red Hat]
* Rebuild [In progress -- Red Hat]
* Hit a snag with 32-bit ARM.
* Coordinated with Nick Clifton (bintuils) and Jiong Wang.
* Fixed here: https://www.sourceware.org/ml/libc-alpha/2017-07/msg00518.html
* Scratch build relatively clean.
* Final build in-progress here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20482917
* Fix Go 1.9.0 for s390x
* Fix s390x breakage [Done -- jcajka]
https://bugzilla.redhat.com/show_bug.cgi?id=1460254
* Rebuild golang with glibc fixes to get ppc64le builds to pass [Waiting -- jcajka]
* Once glibc finishes building we rebuild this.
Note:
- I'm doing a local rebuild of golang 1.9.0 with the new glibc looking for failures
before jacjka wakes up tomorrow in the European time zone.
--
Cheers,
Carlos.
7:53 p.m.
On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
Note:
- I'm doing a local rebuild of golang 1.9.0 with the new glibc looking for failures
before jacjka wakes up tomorrow in the European time zone.
This test shows we have one last ppc64le failure for goland 1.9.0
which I've notified jcajka about :-)
--
Cheers,
Carlos.
6:01 a.m.
On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
> On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
>> If we're lucky we can get everything ready for the 12th, but we might
>> need another day or two given how long it takes to build gcc on all
>> the arches.
>
> We are getting more luck. We'll see how tomorrow goes.
ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
the final golang rebuild with a fixed glibc (ppc64le failures fixed).
Status update:
* Get the gcc trunk patch into F27 gcc. [Done]
* Rebuild glibc [Done]
* Fix Go 1.9.0 [In progress... | jcajka]
* Build in progress.
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
--
Cheers,
Carlos.
6:25 a.m.
On to, 13 heinä 2017, Carlos O'Donell wrote:
On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
> On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
>> On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
>>> If we're lucky we can get everything ready for the 12th, but we might
>>> need another day or two given how long it takes to build gcc on all
>>> the arches.
>>
>> We are getting more luck. We'll see how tomorrow goes.
>
> ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
> the final golang rebuild with a fixed glibc (ppc64le failures fixed).
Status update:
* Get the gcc trunk patch into F27 gcc. [Done]
* Rebuild glibc [Done]
* Fix Go 1.9.0 [In progress... | jcajka]
* Build in progress.
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
Thanks. I started freeipa rebuild and ppc64le build passed this time:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494649
--
/ Alexander Bokovoy
6:37 a.m.
On Thursday, 13 July 2017 at 13:25, Alexander Bokovoy wrote:
On to, 13 heinä 2017, Carlos O'Donell wrote:
> On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
> > On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
> > > On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
> > > > If we're lucky we can get everything ready for the 12th, but we
might
> > > > need another day or two given how long it takes to build gcc on all
> > > > the arches.
> > >
> > > We are getting more luck. We'll see how tomorrow goes.
> >
> > ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
> > the final golang rebuild with a fixed glibc (ppc64le failures fixed).
>
> Status update:
>
> * Get the gcc trunk patch into F27 gcc. [Done]
>
> * Rebuild glibc [Done]
>
> * Fix Go 1.9.0 [In progress... | jcajka]
>
> * Build in progress.
> https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
Thanks. I started freeipa rebuild and ppc64le build passed this time:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494649
Excellent work! Big kudos to everyone involved.
Regards,
Dominik
--
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
7:05 a.m.
----- Original Message -----
From: "Carlos O'Donell" <carlos(a)redhat.com>
To: "Florian Weimer" <fweimer(a)redhat.com>, "Development discussions
related to Fedora"
<devel(a)lists.fedoraproject.org>, "Jakub Jelinek"
<jakub(a)redhat.com>, "Jakub Cajka" <jcajka(a)redhat.com>
Cc: "Jeff Law" <law(a)redhat.com>, "Stephen Gallagher"
<sgallagh(a)redhat.com>
Sent: Thursday, July 13, 2017 1:01:03 PM
Subject: Re: Fedora 27 mass rebuild at risk
On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
> On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
>> On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
>>> If we're lucky we can get everything ready for the 12th, but we might
>>> need another day or two given how long it takes to build gcc on all
>>> the arches.
>>
>> We are getting more luck. We'll see how tomorrow goes.
>
> ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
> the final golang rebuild with a fixed glibc (ppc64le failures fixed).
Status update:
* Get the gcc trunk patch into F27 gcc. [Done]
* Rebuild glibc [Done]
* Fix Go 1.9.0 [In progress... | jcajka]
* Build in progress.
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
Built, https://koji.fedoraproject.org/koji/taskinfo?taskID=20494945
JC
>
> --
> Cheers,
> Carlos.
>
7:57 a.m.
On 07/13/2017 07:01 AM, Carlos O'Donell wrote:
On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
> On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
>> On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
>>> If we're lucky we can get everything ready for the 12th, but we might
>>> need another day or two given how long it takes to build gcc on all
>>> the arches.
>>
>> We are getting more luck. We'll see how tomorrow goes.
>
> ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
> the final golang rebuild with a fixed glibc (ppc64le failures fixed).
Status update:
* Get the gcc trunk patch into F27 gcc. [Done]
* Rebuild glibc [Done]
* Fix Go 1.9.0 [In progress... | jcajka]
* Build in progress.
https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
Status update:
Time is 9:00am EDT.
* gcc - Ready. Confirmed by jakub.
* glibc - Ready. Confirmed by myself.
* golang - Ready. Confirmed by jcajka.
We are ready for mass rebuild.
--
Cheers,
Carlos.
8:21 a.m.
On Thu, Jul 13, 2017 at 08:57:52AM -0400, Carlos O'Donell wrote:
On 07/13/2017 07:01 AM, Carlos O'Donell wrote:
> On 07/12/2017 08:10 PM, Carlos O'Donell wrote:
>> On 07/11/2017 09:48 PM, Carlos O'Donell wrote:
>>> On 07/11/2017 12:37 AM, Carlos O'Donell wrote:
>>>> If we're lucky we can get everything ready for the 12th, but we
might
>>>> need another day or two given how long it takes to build gcc on all
>>>> the arches.
>>>
>>> We are getting more luck. We'll see how tomorrow goes.
>>
>> ETA for mass rebuild readiness tomorrow morning EDT after jcajka finishes
>> the final golang rebuild with a fixed glibc (ppc64le failures fixed).
>
> Status update:
>
> * Get the gcc trunk patch into F27 gcc. [Done]
>
> * Rebuild glibc [Done]
>
> * Fix Go 1.9.0 [In progress... | jcajka]
>
> * Build in progress.
> https://koji.fedoraproject.org/koji/taskinfo?taskID=20494275
>
Status update:
Time is 9:00am EDT.
* gcc - Ready. Confirmed by jakub.
* glibc - Ready. Confirmed by myself.
* golang - Ready. Confirmed by jcajka.
We are ready for mass rebuild.
Kudos for the great work, thanks!!
Pierre
12:07 p.m.
* gcc - Ready. Confirmed by jakub.
* glibc - Ready. Confirmed by myself.
* golang - Ready. Confirmed by jcajka.
We are ready for mass rebuild.
Thanks for these awesome work to every one involved.
1:28 p.m.
On Thu, 2017-07-13 at 11:07 -0600, William Moreno wrote:
* gcc - Ready. Confirmed by jakub.
* glibc - Ready. Confirmed by myself.
* golang - Ready. Confirmed by jcajka.
We are ready for mass rebuild.
Thanks for these awesome work to every one involved.
I suspect the current mess with mariadb may cause significant issues
for the rebuild.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9:09 a.m.
On Fri, Jul 07, 2017 at 02:53:36PM +0200, Florian Weimer wrote:
We currently have an invalid IFUNC resolver in libgcc.a on POWER
(rhbz#1467526). glibc in rawhide recently started linking that into the
library and there are significant problems with that (rhbz#1467518).
I'll be on PTO next week, and it does not seem likely that this is going
to be resolved upstream before that. If upstream (both glibc GCC are
involved) don't come up with a solution, I'm not sure
If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
least the following packages right after that because they have a
GLIBC_2.26 symbol version dependency:
inn-2.6.1-6.fc27.src.rpm
remctl-3.13-4.fc27.src.rpm
sudo-1.8.20p2-1.fc27.src.rpm
tmux-2.5-1.fc27.src.rpm
unbound-1.6.4-1.fc27.src.rpm
xorg-x11-server-1.19.3-6.fc27.src.rpm
Besides the glibc downgrade, I'm not aware of anything else we could do
to get ready for the mass rebuild in time.
So, I had a look at https://bugzilla.redhat.com/show_bug.cgi?id=F26FTBFS,
and the situation is not good :( There's 621 open bugs on that list,
and it's quite likely most of those packages will FTBFS on 27 too.
All packagers should pitch in to reduce this list before the mass rebuild
starts.
Zbyszek
12:48 a.m.
Dne 12.7.2017 v 16:09 Zbigniew Jędrzejewski-Szmek napsal(a):
On Fri, Jul 07, 2017 at 02:53:36PM +0200, Florian Weimer wrote:
> We currently have an invalid IFUNC resolver in libgcc.a on POWER
> (rhbz#1467526). glibc in rawhide recently started linking that into the
> library and there are significant problems with that (rhbz#1467518).
>
> I'll be on PTO next week, and it does not seem likely that this is going
> to be resolved upstream before that. If upstream (both glibc GCC are
> involved) don't come up with a solution, I'm not sure
>
> If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
> least the following packages right after that because they have a
> GLIBC_2.26 symbol version dependency:
>
> inn-2.6.1-6.fc27.src.rpm
> remctl-3.13-4.fc27.src.rpm
> sudo-1.8.20p2-1.fc27.src.rpm
> tmux-2.5-1.fc27.src.rpm
> unbound-1.6.4-1.fc27.src.rpm
> xorg-x11-server-1.19.3-6.fc27.src.rpm
>
> Besides the glibc downgrade, I'm not aware of anything else we could do
> to get ready for the mass rebuild in time.
So, I had a look at https://bugzilla.redhat.com/show_bug.cgi?id=F26FTBFS,
and the situation is not good :( There's 621 open bugs on that list,
and it's quite likely most of those packages will FTBFS on 27 too.
There used to be times, when FTBFS packages were remove once in a while ...
Vít
9:31 a.m.
On Thu, Jul 13, 2017 at 07:48:00AM +0200, Vít Ondruch wrote:
Dne 12.7.2017 v 16:09 Zbigniew Jędrzejewski-Szmek napsal(a):
> On Fri, Jul 07, 2017 at 02:53:36PM +0200, Florian Weimer wrote:
>> We currently have an invalid IFUNC resolver in libgcc.a on POWER
>> (rhbz#1467526). glibc in rawhide recently started linking that into the
>> library and there are significant problems with that (rhbz#1467518).
>>
>> I'll be on PTO next week, and it does not seem likely that this is going
>> to be resolved upstream before that. If upstream (both glibc GCC are
>> involved) don't come up with a solution, I'm not sure
>>
>> If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
>> least the following packages right after that because they have a
>> GLIBC_2.26 symbol version dependency:
>>
>> inn-2.6.1-6.fc27.src.rpm
>> remctl-3.13-4.fc27.src.rpm
>> sudo-1.8.20p2-1.fc27.src.rpm
>> tmux-2.5-1.fc27.src.rpm
>> unbound-1.6.4-1.fc27.src.rpm
>> xorg-x11-server-1.19.3-6.fc27.src.rpm
>>
>> Besides the glibc downgrade, I'm not aware of anything else we could do
>> to get ready for the mass rebuild in time.
> So, I had a look at https://bugzilla.redhat.com/show_bug.cgi?id=F26FTBFS,
> and the situation is not good :( There's 621 open bugs on that list,
> and it's quite likely most of those packages will FTBFS on 27 too.
There used to be times, when FTBFS packages were remove once in a while ...
Even assuming that we started the removal process for those packages,
it's not going to happen today, and IIUC, the mass rebuild is supposed
to start real soon now. The rebuild is supposed to test recent changes in
gcc/glibc/whatever and uncover issues, so it'll not help if
so many packages are failing to build because of other reasons.
Zbyszek
10:20 a.m.
Just to don't confuse you:
I kinda used your Mass Rebuild for my intensions - updgrade of MariaDB
library. So there will be some packages broken by me.
But we actively monitoring and fixing them.
I be glad, if the Mass Rebuild started *after* this build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20495924, however s390
seems stuck for half an hour by now :(
But go on, star when you need, don't get blocked by me.
Thanks! :)
--
Michal Schorm
Associate Software Engineer
Core Services - Databases Team
Red Hat
On Thu, Jul 13, 2017 at 4:31 PM, Zbigniew Jędrzejewski-Szmek <
zbyszek(a)in.waw.pl> wrote:
On Thu, Jul 13, 2017 at 07:48:00AM +0200, Vít Ondruch wrote:
>
>
> Dne 12.7.2017 v 16:09 Zbigniew Jędrzejewski-Szmek napsal(a):
> > On Fri, Jul 07, 2017 at 02:53:36PM +0200, Florian Weimer wrote:
> >> We currently have an invalid IFUNC resolver in libgcc.a on POWER
> >> (rhbz#1467526). glibc in rawhide recently started linking that into
the
> >> library and there are significant problems with that (rhbz#1467518).
> >>
> >> I'll be on PTO next week, and it does not seem likely that this is
going
> >> to be resolved upstream before that. If upstream (both glibc GCC are
> >> involved) don't come up with a solution, I'm not sure
> >>
> >> If we downgrade glibc to 2.25 in rawhide, we will have to rebuild at
> >> least the following packages right after that because they have a
> >> GLIBC_2.26 symbol version dependency:
> >>
> >> inn-2.6.1-6.fc27.src.rpm
> >> remctl-3.13-4.fc27.src.rpm
> >> sudo-1.8.20p2-1.fc27.src.rpm
> >> tmux-2.5-1.fc27.src.rpm
> >> unbound-1.6.4-1.fc27.src.rpm
> >> xorg-x11-server-1.19.3-6.fc27.src.rpm
> >>
> >> Besides the glibc downgrade, I'm not aware of anything else we could
do
> >> to get ready for the mass rebuild in time.
> > So, I had a look at https://bugzilla.redhat.com/
show_bug.cgi?id=F26FTBFS,
> > and the situation is not good :( There's 621 open bugs on that list,
> > and it's quite likely most of those packages will FTBFS on 27 too.
>
> There used to be times, when FTBFS packages were remove once in a while
...
Even assuming that we started the removal process for those packages,
it's not going to happen today, and IIUC, the mass rebuild is supposed
to start real soon now. The rebuild is supposed to test recent changes in
gcc/glibc/whatever and uncover issues, so it'll not help if
so many packages are failing to build because of other reasons.
Zbyszek
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
2476
days inactive
2482
days old
27 comments
15 participants
participants (15)
-
Adam Williamson -
Alexander Bokovoy -
Carlos O'Donell -
Dan Horák -
Dominik 'Rathann' Mierzejewski -
Florian Weimer -
Jakub Cajka -
Matthew Miller -
Michal Schorm -
Peter Robinson -
Pierre-Yves Chibon -
Richard Hughes -
Vít Ondruch -
William Moreno -
Zbigniew Jędrzejewski-Szmek