Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

odoo-15: wkhtmltopdf - account payment - permissions #4

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

adriresu
Copy link
Contributor

No description provided.

@dalonsod dalonsod changed the title [WIP] wkhtmltopdf - account payment - permissions [WIP] odoo-15: wkhtmltopdf - account payment - permissions Jun 15, 2023
@dalonsod
Copy link
Contributor

Every change worked as expected 👏🏽, but Odoo execution error is raised, because of pyopenssl incompatibility, maybe with new libssl apt package for wkhtmltopdf.

Fixed upgrading pyopenssl python library and then downgrading cryptography:

  • pip install -U pyopenssl==23.2.0
  • pip install -U cryptography==38.0.2

Original error: https://stackoverflow.com/questions/73830524/attributeerror-module-lib-has-no-attribute-x509-v-flag-cb-issuer-check

Later error once pyopenssl is updated: https://askubuntu.com/questions/1452610/modulenotfounderror-no-module-named-cryptography-hazmat-backends-openssl-x509

With this fix, Odoo works, as far as I've tested, but some modules that depend on SSL and cryptography features should be tested as well.

Then, these two pip commands should be added to Dockerfile once requirements.txt files have been processed IMO. And these lines could be better added in the same commit of wkhtmltopdf changes.

cc @ChristianSantamaria

@adriresu adriresu changed the title [WIP] odoo-15: wkhtmltopdf - account payment - permissions odoo-15: wkhtmltopdf - account payment - permissions Jul 26, 2023
@dalonsod
Copy link
Contributor

dalonsod commented Feb 8, 2024

The error described above raises again when deploying today this Dockerfile.

I've notice that requests-pkcs12 package in most recent version forces again cryptography upper version, so that workaround should fail again.

It seems that we should add to "custom python package versions" requests-pkcs12==1.16 ... and move the Dockerfile special line at the end of the file, once every requirements.txt files (even OCA ones) are completed.

I'll make another test and verify. But it could break again later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants