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
qesteidutil: Fixes build from Qt upgrade. #46083
Conversation
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: qesteidutil Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: qesteidutil Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: qesteidutil Partial log (click to expand)
|
Since this is a security-sensitive application, we should only apply appstream patches, not try to make our own, so I think it's fine. |
Now I may be overly cautious here, but after applying the patch it's not the officially released version any more, so we should even think about marking it as insecure and warning users about that. After all it's a government-sponsored app related to electronic id cards, and users deserve to know they're not installing the official release (which unfortunately doesn't build). |
I was about to open an issue on their repo, but first I was prompted to read the guidelines.
So yeah, it looks like this already isn't official. Though I additionally agree that we shouldn't willy-nilly patch this! @jagajaga you are marked as the maintainer. Any input? Do you have any association with this software? Are you a user? |
Instead of patching, we could use the latest git revision, name the nixpkgs version |
We are fetching it from "official" repository, so everything is alright. I'm using this software everyday on nixos. Let's merge this. |
Sorry this got delayed. Since the maintainer approves, let's merge it. |
(cherry picked from commit ef2b217)
backported: 7c7f962 |
Motivation for this change
Plowing through #45960 failures.
This is (with at least another failure) fallout from Qt 5.10 -> 5.11 from June.
The patch does not strictly address the issue, but has been judged (by me) to be fine; the actual intended fix is minimal, and the value of having one fewer failure is good. If it is judged not to be fine, cutting the fix and keeping the header changes in a custom patch can be done.
It'll need cherry-picking to release-18.09
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)#44047 stops me from testing this :/.