-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app-office/libreoffice: Backport upstream patch to allow compilation with GCC 14 #36049
Conversation
d5cf64e
to
b419abe
Compare
Pull Request assignmentSubmitter: @0xr0bert app-office/libreoffice: @gentoo/office Linked bugsBugs linked: 928152 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2024-04-01 19:22 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. No need for new revisions for this as it's a build-time only fix and it's not a correctness issue at all (I mean, it is, but if it builds, it's because the transitive include got picked up, so no runtime behaviour diff. before/after).
Could you fix that and then lgtm?
b419abe
to
6cfc834
Compare
All done @thesamesam |
Pull request CI reportReport generated at: 2024-04-02 16:40 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thesamesam, @0xr0bert: As far as I can see this is just duplicating what we already have as libreoffice-7.6.5.2-gcc14.patch
but got dropped from 7.6.6.3
because it was not applied to 7.6.9999
and 7.6.5.2
ebuild had said # upstream
only, instead of which branch this was coming from.
So, neither do we have to add the patch to FILESDIR in the first place nor should we touch the stable 7.6.4.1
as a matter of principle. We only need to re-add the patch to 7.6.6.3
, there's probably not going to be another release spun from 7.6.9999
.
See also commit 321f0ca
Also, since |
Thanks @a17r Should it not be applied to the stable 7.6.4.1? If not, could we add specify as a dependency that gcc < 14. Should it not also be added to 7.6.9999 as well as 7.6.6.3? |
7.6.4.1 does not need any change as long as GCC-14 does not even have any keywords. No one should try this with arch-only and if they do, they may apply user patches. It is just busywork for us and we do not touch stable ebuilds unless really really necessary. For 7.6.9999 it is likely to be dropped soon, or if upstream decide to backport, it was again just busywork for us when it fails to apply the patch for everyone, not just GCC-14 users. |
…14 compilation Closes: https://bugs.gentoo.org/928152 Signed-off-by: Robert Greener <me@r0bert.dev>
6cfc834
to
2c36b9e
Compare
I have done as you've suggested @a17r and it compiles with GCC 14 |
Pull request CI reportReport generated at: 2024-04-02 21:00 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Thank you! Yeah, when I looked at it before, I was convinced it'd been backported everywhere upstream. Apparently not. |
Bug: https://bugs.gentoo.org/928152