FS#41109 - [calibre] Cannot build without pyqtconfig

Attached to Project: Community Packages
Opened by Vorbote (vorbote) - Sunday, 06 July 2014, 12:47 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 09 August 2014, 17:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The PyQT binaries in the repo have been compiled in such way that they don't support compiling calibre. The PyQT documentation[1] states that pyqtconfig will be dropped from pyqt5 and that you can drop it from pyqt4 as well by compiling it using the configure-ng.py script. This is the case here.

I discovered this when trying to update calibre to the latest version using the ABS PKGBUILD.

[1] http://pyqt.sourceforge.net/Docs/PyQt4/build_system.html
This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 09 August 2014, 17:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in calibre 1.205
Comment by Andrea Scarpino (BaSh) - Monday, 21 July 2014, 17:18 GMT
  • Field changed: Summary ([calibre] Calibre is impossible to build due to FS#41108 → [calibre] Cannot build without pyqtconfig)
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages → Upstream Bugs)
  • Field changed: Severity (Critical → High)
  • Task assigned to Jelle van der Waa (jelly)
Jelly you need to put some pressure to upstream dev about this.
Comment by Doug Newgard (Scimmia) - Tuesday, 22 July 2014, 00:30 GMT
The upstream devs won't support anyone but themselves building the software.
Comment by Doug Newgard (Scimmia) - Thursday, 24 July 2014, 14:53 GMT
I'm guessing this won't be solved until Calibre 2.0 switches to QT5. It's currently in beta.
Comment by Jelle van der Waa (jelly) - Thursday, 24 July 2014, 21:40 GMT
Thanks for the information, I'll check if beta build is packagable since I am not in the position of patching calibre :)

Beta build link http://www.mobileread.com/forums/showthread.php?t=242223
Comment by Jelle van der Waa (jelly) - Wednesday, 30 July 2014, 19:21 GMT
Ok the beta builds have no source code, trying to build the git snapshot qt5 branch but plugins aren't supported so I'm not sure how useful it would be. When he releases an rc I can consider putting it in the repos.
Comment by gfrito (gfrito) - Friday, 01 August 2014, 12:42 GMT
It looks like he just released a beta source code archive. I uploaded "calibre-beta" to the AUR (it's just your package with a few new qt5 dependencies and removal of an unneeded patch).
Comment by Doug Newgard (Scimmia) - Friday, 01 August 2014, 22:22 GMT
More and more plugins are getting ported. I only use 2, and both have been updated, so I thought I'd give it a try. Seems to be running fine.
Comment by Jelle van der Waa (jelly) - Saturday, 02 August 2014, 10:02 GMT
Thanks for the information, I was about to give the beta build another try this weekend, so hopefully I can upload 1.2beta today
Comment by Doug Newgard (Scimmia) - Saturday, 02 August 2014, 14:17 GMT
I have posted a cleaned-up PKGBUILD in the AUR comments. It would still use some work on the desktop integration (main problem is that the system python module doesn't get installed). Note that the wrapper script is no longer needed and the patch is removed in favor of sed, but that can easily be remade from the included sed command.
Comment by Jelle van der Waa (jelly) - Saturday, 02 August 2014, 19:54 GMT
Thanks for the PKGBUILD, I've updated the package in [community]
Comment by Doug Newgard (Scimmia) - Saturday, 02 August 2014, 20:47 GMT
You didn't use my PKGBUILD, though. There are a number of unncecssary deps in yours (poppler-qt, python2-beautifulsoup3, and libunrar), and a number of the sed expressions do nothing at all.
Comment by Doug Newgard (Scimmia) - Sunday, 03 August 2014, 12:50 GMT
Nearly there :). pyqt4-common is still in the dep list and not need (I didn't notice that before), and a new dep, qt5-svg, is missing. Also missing are python2-chardet and python2-html5lib, which are needed when you remove the bundled versions.

I'm going to request removal of the beta version from the AUR now that it's in Community.
Comment by Patrick Houle (Buddlespit) - Sunday, 03 August 2014, 14:18 GMT
This shouldn't be in Community until it's out of beta. I just spent a solid two hours trying to figure out why my newly updated Calibre 1.204 wasn't able to convert and move books to my Kindle. Please move this to Community-testing until it's out of beta, so those of us who aren't as arch-savy as the maintainer don't end up with broken 'Release' applications.
Comment by Doug Newgard (Scimmia) - Sunday, 03 August 2014, 14:37 GMT
@Buddlespit, it's not going to be in beta long, and it's only really in beta now to give plugin authors/maintainers a chance to update their code to be Qt5 compatible. Make sure you have the three packages I mentioned installed and if you still have a problem, tell us what's actually going on.
Comment by Patrick Houle (Buddlespit) - Sunday, 03 August 2014, 14:45 GMT
No, it works now that I've found this bug report and added the three (qt5-svg, python2-chardet and python2-html5lib) missing dependencies. But I think it's still valid to say that until either the PKBUILD or the application itself get's fixed, it shouldn't be a 'Released' application and should reside in testing until it's stable to install all by it's lonesome. Meaning without having to look thru bug reports or googling a fix. I stumbled upon this bug report coming in to report a bug.
Comment by Jelle van der Waa (jelly) - Sunday, 03 August 2014, 15:36 GMT
[community-testing] release might have been smarter, but it was pretty important to get a new working calibre package in [community]. Sadly I couldn't fix the current calibre code to work with the new pyqt4 and upstream developer won't fix his code for pyqt4.

Anyway I am putting -2 out which adds the three missing deps.

Loading...