| Summary: | Failed to emerge app-text/calibre-0.6.16 - PoDoFo not found on your system | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | saft <safttuete> |
| Component: | Current packages | Assignee: | Zac Medico <zmedico> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InVCS |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
emerge faillog calibre 0.6.16 patch for optional podofo build Ebuild patch with new use flag podofo |
||
Created attachment 205913 [details]
emerge --info
Created attachment 205914 [details]
emerge faillog
This missing dependency is added in calibre-0.6.16-r1. Thanks for reporting. (In reply to comment #3) > This missing dependency is added in calibre-0.6.16-r1. Thanks for reporting. > Actually that podofo error raised on an optional extension is an upstream bug which was fixed in the trunk and will be in the next version. I fixed my 0.6.16 ebuild with the attached patch on the source. Would be nice to remove that dependency, thanks. Created attachment 206463 [details, diff]
calibre 0.6.16 patch for optional podofo build
(In reply to comment #5) > Created an attachment (id=206463) [details] > calibre 0.6.16 patch for optional podofo build It would be better if we added IUSE="podofo" forcefully disabled it if that USE flag isn't enabled. For example, this is how app-office/scribus in the kde-testing overlay is supposed to work. Created attachment 207226 [details, diff]
Ebuild patch with new use flag podofo
Haven't found that ebuild you mentioned, would this be something like the changes in the attached patch? I like the idea of a use flag, gives more control.
(In reply to comment #7) > Created an attachment (id=207226) [details] > Ebuild patch with new use flag podofo > > Haven't found that ebuild you mentioned, would this be something like the > changes in the attached patch? I like the idea of a use flag, gives more > control. That's good, but we also should modify the build system, to ensure that the podofo binding isn't built when podofo happens to be installed but USE=podofo is disabled. |
Updating calibre from 0.6.11 to 0.6.11 fails with multiple errormsgs.: Traceback (most recent call last): File "setup.py", line 99, in <module> sys.exit(main()) File "setup.py", line 85, in main command.run_all(opts) File "/var/tmp/portage/app-text/calibre-0.6.16/work/calibre/setup/__init__.py", line 158, in run_all self.run_cmd(self, opts) File "/var/tmp/portage/app-text/calibre-0.6.16/work/calibre/setup/__init__.py", line 154, in run_cmd cmd.run(opts) File "/var/tmp/portage/app-text/calibre-0.6.16/work/calibre/setup/extensions.py", line 226, in run raise Exception(ext.error) Exception: ('PoDoFo not found on your system. Various PDF related', ' functionality will not work. Use the PODOFO_INC_DIR and', ' PODOFO_LIB_DIR environment variables.') * * ERROR: app-text/calibre-0.6.16 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3029: Called distutils_src_compile * environment, line 743: Called die * The specific snippet of code: * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed"; * The die message: * Building failed Reproducible: Always Steps to Reproduce: emerge calibre Actual Results: fails to emerge Expected Results: emerge ;)