Re: List of long term FTBFS packages to be retired in August

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

 





On Tue, 25 Jul 2023 at 11:54, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:
On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer <fweimer@xxxxxxxxxx> wrote:
>
> * Josh Boyer:
>
> > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
> >>
> >> On 25. 07. 23 16:42, Florian Weimer wrote:
> >> > * Miro Hrončok:
> >> >
> >> >> glibc32                                   codonell, fweimer, jakub, mcermak
> >> >
> >> > Is this about FTBFS issues?  There isn't any recent build failure in
> >> > Koji, so I don't get why it's on this list?
> >>
> >> The build currently in Rawhide was done on Fedora 36 which is end of life.
> >>
> >> Apparently the release engineering team has not rebuilt this package in a mass
> >> rebuild at least since Fedora 35.
> >>
> >> To remove it from the list, build the package on Rawhide please.
> >
> > Or we could not, and drop i686 completely.
>
> If we drop glibc32, we can't build any 32-bit code at all because GCC
> will no longer support -m32.  In this regardm x86-64 is different than
> the other Fedora architectures which can target bare metal 32-bit even
> from 64-bit-only compilers.
>
> Are bootloaders fully treated as firmware and no longer built by Fedora?
> At least the shim package does not come with corresponding source code
> AFAICS.  But I expect that there are other 32-bit pre-boot packages that
> we still rebuild.
>
> We need to fix this GCC build issue for CentOS 10 eventually, and at
> that point, we won't need glibc32 anymore.  It's been a constant source
> of annoyance.

Necessity is the mother of all invention.  If you need this solved by
CentOS Stream 10, you really want to solve it now and get that
solution into F39 or F40 at the latest.


As much as I would like to see the i686 problem dealt with finally, I am not sure what is done with a fundamental change like this after the closing period for such changes for Fedora 39. [It does lead to a funny problem.. if i686 were to get removed after the mass rebuild because a cascade of FTBFS or other reasons.. does FESCO need a change proposal :)]

 
josh
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[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