Dangerzone image doesn't build (errors during libmupdfcpp.so compilation) #750
Comments
|
Thanks for pointing out these errors. I hoped they would be transient, but they still persist. Also, I can reproduce them in a vanilla Alpine Linux container. Since we have not changed something in the way we build our container images in the past few days, I opened an issue in PyMuPDF's bug tracker: pymupdf/PyMuPDF#3279 |
stepnem
added a commit
to stepnem/dangerzone
that referenced
this issue
Mar 22, 2024
The problem (MuPDF C++ bindings generation breakage) was apparently caused by a recent libclang update on pypi, and fixed in the 1.24.0 release[1]. Fixes freedomofpress#750 [1]: pymupdf/PyMuPDF#3279
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As witnessed in the last two Tests runs (last one),
build-image.pynow fails during the "Preparing metadata" step,in particular there are errors (e.g.,
'FzStextPage' does not name a type; did you mean 'fz_stext_page'?)when compiling
libmupdfcpp.so.The text was updated successfully, but these errors were encountered: