-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
python3Packages.xen: init at 4.19.0 #345171
Conversation
@@ -17550,6 +17550,10 @@ self: super: with self; { | |||
inherit (pkgs) graphviz; | |||
}; | |||
|
|||
xen = toPythonModule (pkgs.xen-slim.override { |
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.
Using xen-slim causes duplication of xen package in system closure, but xen can't be built with internal qemu on latest python.
I haven't found a good way to only build python package out of xen source tree, but it might be made better in future with dedicated python output.
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.
I'm still not exactly sure why we're shipping 24.11 with a clearly broken Meson. Have you tried using 3.12 but overriding the python package to include setuptools
? I tried it myself a few weeks ago but didn't have any success, but it's probably because I'm not very familiar with the python ecosystem.
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.
I have tried adding setuptools to meson package itself, and it didn't work for me. Meson does something clever/stupid and can't find setuptools this way.
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.
...Python module is not required for qubes, as qubes has its own qubes-vmm-xen based off xen-slim, and we can only include relevant xen changes, but I wanted to add xen python package itself for easier testing.
bb21ee1
to
561007c
Compare
So, if I understood this correctly, |
python3Packages.xen will is pinned to whatever version this package set is pinned to (python311Packages set will have it built with python 3.11, python312Packages with python 3.12, python310 with python 3.10). So, xen will be built for every supported python version here, and this is why I would like if we manage to build python package without building rest of xen. |
ebf4d6b
to
7b9c9c9
Compare
Why... Result of nixpkgs-review pr 345171: 1 package marked as broken and skipped: 8 packages failed to build:
|
Huh, did it only fail with 4.17? |
Yep, only on 4.17. So, adding setuptools breaks distutils?.. |
Can we add a version condition to include |
7b9c9c9
to
ec70660
Compare
Result of 1 package marked as broken and skipped:
8 packages failed to build:
76 packages built:
|
Oh, it has failed again? Didn't noticed that, I thought everything is ok. Ah, that's 4.17-slim that's failing, due to newer python being used. I'll just switch it to python311 for 4.17-slim build. |
ec70660
to
34c22dd
Compare
34c22dd
to
8de0512
Compare
Result of 1 package marked as broken and skipped:
89 packages built:
|
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.
Looks good, and build seems happy with using Python311 for 4.17*
8de0512
to
4d67e28
Compare
Result of 1 package marked as broken and skipped:
67 packages failed to build:
22 packages built:
...forgot about overrides in xen/packages.nix |
4d67e28
to
26fb54e
Compare
Result of 1 package marked as broken and skipped:
89 packages built:
|
Description of changes
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.