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
calibre 4.23.0 -> 5.10.1 #106550
calibre 4.23.0 -> 5.10.1 #106550
Conversation
I was able to get past this error by specifying the appropriate platform tag: ento@e9969b9 (only tested the Q_PID is typedef'd based on the active platform tag (note: the linked repo is a mirror): I'm not sure how Calibre's build system is bypassing/specifying this. (Nor am I entirely sure if this is the right approach. Specifying the platform tag was the suggested fix 15 years ago.) Another fix before nix-build succeeded: add zeroconf to dependencies: ento@783b0ff This was to address "No module named 'zeroconf'"
Another fix before I was able to launch calibre: update PyQt5 to use sip5: ento@5d60a5c This was to address "RuntimeError: the sip module implements API v12.0 to v12.7 but the progress_indicator module requires API v12.8"
^That commit shouldn't be used as-is - there's already a draft PR that updates sip to 5.x and I think we should coordinate with @FRidh on how to do it (whether to add a new pythonPackages.sip5 package etc). |
@mexisme Just saw your comment in the linux-surface PR. Coincidentally I just searched for Calibre updates in nixpkgs a couple days ago. The people here might have work you can use, in case you didn't see this? :) |
@ento Thanks for looking into this. I was able to build and run calibre 5.6 from your calibre5-pyqt5-sip5 branch, so I guess the next step is to decide what to do with sip5. |
Thanks,@hpfr. |
Just an FYI: I've been working on building Calibre 5.81 in a personal overlay with personal packages, and have gotten sip5, pyqt-builder and pyqt5-sip building easily with fetchPypi. I was going to move from my personal packages into a nixpkgs fork to solve this, as it was just getting too messy. @hpfr kindly pointed this PR to me, and wondered if anyone's interested in help? |
This PR now builds thanks to @ento's commits. The next step is to decide what to do with sip. This PR keeps sip version 4 and adds sip5 as a new package, but there is also a PR that just replaces sip 4 with sip 5. |
Brilliant, and thanks for your efforts!
That's good to see; sip4 doesn't seem to be supported upstream, any more. |
Can we close this? |
This is waiting for #108041, I will un-draft this PR when it gets merged. |
FYI: #108041 was just merged. |
Result of 4 packages built:
|
What's going on with grahamcofborg-eval? It's been pending for 12 hours. |
@ofborg eval |
I think it would be a good idea if someone who has experience with calibre could look at this and confirm that everything is looking good. |
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.
Overall it looks good to me.
|
||
meta = with lib; { | ||
description = "PEP 517 compliant build system for PyQt"; | ||
homepage = "https://pypi.org/project/PyQt-builder/"; |
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 would not indent like that but it is a detail.
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.
Unindent this. We don't need pretty-prinmting, seriously.
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.
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.
What do you mean with "indent"?
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'd assume they're talking about the alignment (where the equal signs are all lined up).
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'll remove it, but I've seen many packages that way.
description = "PEP 517 compliant build system for PyQt"; | ||
homepage = "https://pypi.org/project/PyQt-builder/"; | ||
license = licenses.gpl3Only; | ||
platforms = platforms.all; |
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.
platforms = platforms.all; |
Set by buildPythonPackage to the correct platforms.
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.
Fixed
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 3 packages built:
The following issues got detected with the above build packages. python37Packages.pyqt-builder: Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
|
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 4 packages built:
The following issues got detected with the above build packages. python37Packages.pyqt-builder: Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
|
Co-authored-by: ento <ento+github@i.pearlwaffles.xyz> Co-authored-by: Eduardo Sánchez Muñoz <esm@eduardosm.net>
Fixed |
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 4 packages built:
|
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)