Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33392 - [calibre] package does not contain compiled bytecode
Attached to Project:
Community Packages
Opened by Stefano Sanfilippo (esseks) - Monday, 14 January 2013, 16:23 GMT
Last edited by Giovanni Scafora (giovanni) - Friday, 18 January 2013, 08:53 GMT
Opened by Stefano Sanfilippo (esseks) - Monday, 14 January 2013, 16:23 GMT
Last edited by Giovanni Scafora (giovanni) - Friday, 18 January 2013, 08:53 GMT
|
DetailsDescription: calibre-0.9.14-1 ships without .pyc/.pyo compiled bytecode and startup is very slow. Batch operations are also affected, as Calibre spawns a worker (calibre-parallel) for each job. An option is to generate bytecode by hand using compileall, but I don't fancy having untracked files under /lib.
So, patch below adds the relevant commands to produce compiled bytecode. 
compile.patch
(0.5 KiB)
|
This task depends upon
Closed by Giovanni Scafora (giovanni)
Friday, 18 January 2013, 08:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in calibre-0.9.15
Friday, 18 January 2013, 08:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in calibre-0.9.15
Comment by Stefano Sanfilippo (esseks) -
Monday, 14 January 2013, 16:28 GMT
Sorry, forgot to add a title and now I can't modify this bug report. Something like "package does not contain compiled bytecode" would do.