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
Replay Qt 5.12.3 version bump #66266
Conversation
@GrahamcOfBorg test plasma5 |
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.
Validated that (1) by reverting #65526 this bump would fail, and that (2) it doesn't fail as it is.
This is good to go.
@samueldr Thanks for checking this out for me! 😄 |
This is slightly off-topic but I have a shit-ton of changes (frameworks, plasma, applications) that I wanted to see if it had to go into staging, only to see that various people had already done all the work. Gaaaarrrggghhhhh. Note to future self - check staging before taking on bigger bits. |
It won't build on darwin: https://hydra.nixos.org/build/98889958 |
Most likely we need to update the qtbase patch to fix the error, I think |
BTW, I see several Qt apps now fail to build with "incomplete type" messages. I assume it's just some header reorganization and adding includes will fix that relatively easily, as this PR was just a patch-number bump. |
It's now in master, including the problems I posted about. |
Oh, I didn't realize that we have {
libsForQt5 = if stdenv.isDarwin then libsForQt511 else libsForQt512;
} so the breakage of 5.12 on darwin doesn't seem too significant, though |
5.12 has been broken again, nad libsForQt5 has never been switched anyway. This should unblock the nixpkgs channel. Discussion thread: #66266 (comment)
I switched Darwin back to 5.11 for now: 2a79106 🤷♀️ |
I've applied a patch and fixed We have to bump the Qt version on Darwin as Qt 5.11 does not build with latest mesa. |
Motivation for this change
#64598 was reverted for causing segfaults (see #65448). The strict compatibility enforced by #65526 prevents the problem from recurring.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @