Re: Problems with packages compiled with gcc 10.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 19, 2020 at 8:08 PM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>
> On Tue, May 19, 2020 at 11:40:50AM +0200, Fabio Valentini wrote:
> > On Tue, May 19, 2020 at 11:28 AM Vitaly Zaitsev via devel
> > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > Next time FESCo should forbid gcc updates to unreleased versions in
> > > branched Fedora releases.
> > >
> > > Now we need a new mass rebuild in Fedora 32 with fixed gcc 10.1.1 version.
> >
> > As I wrote in my direct response to Guido, doing a mass rebuild for
> > fedora just isn't possible in released branches. So, the best we can
> > do is to deal with issues as people become aware of them and report
> > them, and then rebuild those few broken packages with the "fixed" GCC
> > version, instead of "just rebuild everything because".
> >
> > We also briefly talked about not including pre-release GCC versions in
> > rawhide, but since new GCC versions get almost all their testing only
> > in rawhide, this would inevitably only lead to lower-quality final GCC
> > releases that would then end up in released fedora versions anyway. We
> > (FESCo) were not able to think of a better way to do this.
>
> Well that's one way to look at it.  Another is that I spent half a day
> chasing a bug for one of our users in Fedora 32, and it turned out to
> be caused by GCC.  I *would* have spotted this in Rawhide if it had
> been there for any length of time first.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1835649
>
> You just cannot allow random preproduction GCC into released Fedora.

Well, that's not exactly what happened.
The branch for what would eventually become fedora 32 just inherited a
pre-release GCC version, because that's what was on the master branch
/ in rawhide at the time.

I think we just jad a bit of "bad luck" this time round - the exact
build that was used a period of time (including the mass rebuild, I
think) seems to have produced buggy code in some circumstances. If
those issues had been compile time errors instead of runtime errors,
they would've been caught pretty quickly, but alas ...

Fabio

> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux