![]() |
#16 |
Ex-Helpdesk Junkie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Aaand now tracked by https://bugs.gentoo.org/805965 so hopefully that gets resolved soon.
|
![]() |
![]() |
![]() |
#17 | |||||
Junior Member
![]() Posts: 2
Karma: 10
Join Date: Jul 2021
Device: Kindle
|
Quote:
Quote:
Quote:
"The calibre build doesnt expect it to be anywhere, that would be sip from the pyqt package. It's most likely a problem with the way that gentoo packages and builds PyQt, so you may want to start there, it's not something I can really help with" It's a minor rephrasing, but comes across far less antagonistic and more positive in nature - I know that contributing to open source software can be a massive time sink and is often thankless, but people can easily be put off from helping because they get attacked for asking a question that might seem obvious to some people but isn't for others. The other thing to remember is that this is a public forum - it's not like this was an email sent directly to the developer, the initial question was asked on a relevent thread (I know I got here from searching for the error message). Quote:
Quote:
I do appreciate that there is relevent information in both yours and Kovid's posts, and I don't want this to come across as me being ungrateful - I know that it's no one's job except the relevent package maintainer to sort out build issues like this, but one of the first things I do when debugging an issue (after trying the obvious) is ask to see if anyone else has had a similar issues, and the calibre development forum seems an appropriate place to do this given google searches were coming up with zilch. For reference, the PyQt5 ebuild used a deprecated build system (I'm unsure when it changed from configure.py to sip-build, as old versions of the PyQt5 documentation mentions configure.py), that required updating. Additionally, not all of the flags passed to the old build system directly translated across so there needed to be a little bit of tinkering with configuration flags to ensure that PyQt5 would build properly. Once that's updated in the main portage tree, a calibre ebuild for the latest version (5.24.0) will build OK and the zeroconf errors that were also happening due to a zeroconf update have been fixed thanks to Kovid's dependencies being updated. |
|||||
![]() |
![]() |
Advert | |
|
![]() |
#18 | ||||
Ex-Helpdesk Junkie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
For what it's worth, linux distros have historically messed up calibre in some fairly weird ways, to the point that it was basically impossible to have a distro version that actually worked sanely. This bothered me immensely, since I am a packager for a distro, so I've contributed immensely to calibre development in order to add distro-specific build options, tighten the source build integrations, and take advantage of the python3 migration (which I also helped to massively drive) to sort out (or encourage Kovid to sort out) the status of a number of forked and modified vendor dependencies so that they can use the upstream versions, since patching them out did not in fact actually work. Which ironically caused bugs such as https://bugs.gentoo.org/705088#c3 (9 months of calibre on Gentoo having a broken recipes subsystem and more). I had mentioned this on the forums a couple months prior to that bug report, but at the time I guess it never got submitted as a bug. Kovid is, well, "cautious" about distros. But my packages have never caused him issues (quite the opposite), which I guess earns me a few points. Also I've made it a lot harder for distros to mess up calibre, e.g. the xdg-* hacks every distro had are now obsolete because my personal hack which obviously I believe is the best, is now included in calibre's build system, and it's no longer required to patch calibre to use the system mathjax or liberation-fonts because there are now "python3 setup.py build" options to do that in a supported manner. Speaking of making it harder to mess up calibre packaging, maybe you would like to improve the Gentoo ebuild to run a test phase with the calibre testsuite? It should be quite trivial to run, with the caveat that it needs to run under xvfb-run or some other method of guaranteeing it has an Xorg display. This would have solved a number of Gentoo bugs with missing runtime dependencies or sed lines that malfunctioned when the code they patched no longer applied, but the sed lines themselves began to remove code that the package maintainers never intended it to remove (using patch instead of sed would also help here). Quote:
![]() But really, distros have had since https://github.com/kovidgoyal/calibr...54da9de9267025 to figure out the issue with the build system, and Gentoo has been dealing with it by reverting the change until further notice, the entire time. Quote:
Because I would like to see this fixed, I have provided additional information, but again, you might think that the calibre development forum is an appropriate place to do this, but I posit that the PyQt support channel is also an appropriate place to do this... ... and it becomes an even better place to do it, once the calibre developer claims that it's a sip/pyqt problem and not a calibre one. At that point, it inevitably becomes a bit of a battle of wills to see who will crack first, the questioners who may end up going to upstream PyQt or the application developer who may end up contributing time in researching and debugging a distro's unrelated dependency problems. Not super fun, I suppose, given as far as the application developer is concerned, he provided all the information he had, and told you exactly which component you need to look into to fix it. Quote:
Anyway. Upstream PyQt is the best place to ask about those configuration flags. Really. PLEASE, do ask the PyQt developer about this, he created sip-build and it's his $DAYJOB to support it. If the option doesn't exist, and you need it, then you will need to ask him to add it back anyway. He's not unapproachable. While you're at it, you could ask about any issues you're having with PyQt. EDIT: actually I see you have already asked about this on the mailing list. Sorry. ![]() Last edited by eschwartz; 08-01-2021 at 04:01 PM. |
||||
![]() |
![]() |
![]() |
#19 |
Enthusiast
![]() Posts: 34
Karma: 10
Join Date: Jun 2008
Device: Sony PRS-500
|
I also find it strange that my post was used as an example of "interrogation" . I responded to an error report and an answer to use a -devel package which does not apply to my silly distro despite the exact same error.
Thanks for the the work on this everyone. I had no idea it went this deep into pyqt5 build scripts. Despite my computer science degree and software development career I never took the time to learn and develop in Python. It remains enigmatic to me. Take it easy. Cheers. |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Apple Mac now have a file extension ".iba" for the program "iBooks Author." | brucehobson | Calibre | 3 | 09-15-2014 07:46 PM |
Kindlet gives "Unable to find class Main" | Sothh | Kindle Developer's Corner | 4 | 06-27-2013 08:01 PM |
Custom column: "Updated date", when adding new "versions" of the same file? | enriquep | Library Management | 16 | 11-03-2011 10:46 AM |
"[Error 2] The system cannot find the file specified: u'E:\\'" | Nyssa | Calibre | 3 | 03-17-2011 08:08 PM |