Mass Fortran rebuilds due to new GCC?
kevin at scrye.com
Sun Feb 15 21:05:46 UTC 2015
On Fri, 13 Feb 2015 21:59:06 +0100
Björn Esser <bjoern.esser at gmail.com> wrote:
> Am Freitag, den 13.02.2015, 13:53 -0700 schrieb Kevin Fenzi:
> > On Fri, 13 Feb 2015 12:47:07 -0800
> > Susi Lehtola <jussilehtola at fedoraproject.org> wrote:
> > > Hi,
> > >
> > >
> > > as has happened many times before, the GCC bump in rawhide has
> > > broken all Fortran packages, desperately needing a mass rebuild.
> > Can you expand on the breakage? Is it that they no longer rebuild?
> > Or that they no longer run?
> I think, he's talking about the fact they are segfaulting… ;)
Well, thats not really clear to me at least. "broken" is pretty generic
> > > Unfortunately, rpm is blissfully unaware of any breakage happening
> > > (BZ #1192617) so maintainers won't even know when this breakage
> > > happens.
> > >
> > > Before I start rebuilding packages, are there any plans to do the
> > > rebuilds soon..?
I think the plan was to do one in rawhide as soon as gcc5 is ready.
So, likely sometime in the next few weeks perhaps?
> > There is no mass rebuild this cycle. It would be good to isolate the
> > scope here and see what needs to be rebuilt. Do you have a list of
> > all affected packages or a way to come up with one?
> Why is mass rebuild skipped this time?
Not enough time in the cycle.
> For this particular case it is: repoquery --whatrequires libgfortran
But it sounds like it's a subset of these (only those with .mod files)
that are actually affected?
So, something like:
% repoquery -qf /usr/lib64/gfortran/modules/\*.mod | sort | uniq
And then I suppose everything that buildrequires them?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the devel