-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
pyfa: 2.60.2 -> 2.61.0 #356622
pyfa: 2.60.2 -> 2.61.0 #356622
Conversation
c17ad67
to
e2439b0
Compare
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.
Im getting the following error when trying to build it. It also eats like a solid 12GB of RAM, not sure if that's expected.
error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "wrapGAppsHook" at /home/aki/.cache/nixpkgs-review/pr-356622-2/nixpkgs/pkgs/by-name/py/pyfa/package.nix:7, did you mean "wrapGAppsHook3" or "wrapGAppsHook4"?'
e2439b0
to
1a0cabe
Compare
i'm not sure if I understand why in my local env I was able to build with wrapGAppsHook only, but will take a look at this later. I just switched to version 4, but I wonder if would be better to validate the local version available and decide which to use - what is your take?. in regards to memory, I'm all ear on how to optimize this, the pyinstaller method is taken from pyfa wiki |
1a0cabe
to
fd7eb3e
Compare
made the wrong choice I think, pyfa is gtk3 -- switched to it. |
I'm unsure how other Python based packages handle this, so I guess that's something to look into. I'm going to bed now, if I find time tommorow, I will look into it. |
yeap, while I do see the benefit of compiling it and making sure that all the libraries are properly set, let me see if we can just wrap it and run. |
to no avail, getting all sorts of error and missing dependencies, and can't just install it directly, since it is an externally managed environment. let me know if you have any luck. meanwhile did you manage to run it locally using pyinstaller version? the wrapGAppsHook was solved? |
i just got around to test building this, and got an error. Btw, the reason your GApps thing didnt work is because you arent using the unstable branch. At least im pretty sure you are making and testing this on stable NixOS, but when this gets merged and build, it does so on unstable, so you should use that for making PRs here.
|
Oh, so while my system is running 100% unstable, the branch that I trigger the build process on nixos fork locally was stable, ha! did not realized that. probably also related to this other error you have, gonna switch the branch and test it out later.
btw I do appreciate the the help/directions on it! thanks. |
oddly, rebased the branch against nixos-unstable and built it again without errors, I can't reproduce the errors you got locally. got any other clue of what might be going on? btw, I do have the feeling that I'm building it wrong locally and that is why works here but not for you, I'm using |
fd7eb3e
to
f8ab208
Compare
manually did a check on the subpackages that was included from python3Packages (python312Packages) and the dateutil was indeed incorrect, adjusted to python-dateutil. so that error you had of |
f8ab208
to
74665e7
Compare
and then, just did the nixpkgs-review step (hopefully that is the answer to my previous question about making it reproducible?) |
I'm pretty sure you are supposed to rebase this just against master, that's what it gets merged into when this PR is accepted. PS: Hi Leah c: fancy seeing you here |
d126682
to
cc4d769
Compare
😕 |
You can format it with Edit: if it still doesn't work, maybe your Nit: can you configure your editor to use 2 space indentation in nixpkgs? There are tabs in |
interesting, the code before the review was nixfmt-rfc-style complaint, and my local configuration do use 2 space width; but the last change commited directly from the suggestions 9eba09 was the one. my fault was not rebasing to the very last commit that do introduce the changes, I was under the impression that cc4d769 broke it, but it was 9eba09. Rebasing with the github changes do identify the issue using |
Oh I'm just seeing that the editorconfig check is failing, and nixfmt doesn't fix that. You fixed some whitespace issues but there are 2 tabs which it doesn't like. To convert tabs to 2 spaces you can run |
4c9c721
to
fefc685
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-already-reviewed/2617/2132 |
|
0bf8bc8
to
f05b34d
Compare
rebase against master and push to solve conflict @ maintainers/maintainers-list.nix |
@wolfgangwalther thank you! much appreciated |
switch from appImage to pythonApplication, update from 2.60.2 to 2.61.0
Pyfa Release 2.61.0
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.