-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Always build xmlsec and lxml packages from sources in our images #53137
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
Conversation
This is needed in order to avoid libxml and xmlsec using different version of libxml2 (binary lxml embeds its own libxml2, while xmlsec uses system one). See https://bugs.launchpad.net/lxml/+bug/2110068 Fixes: apache#52539
9c87a09 to
fc27492
Compare
|
Let's see :) |
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, lets see
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 7f5c8db v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
…che#53137) This is needed in order to avoid libxml and xmlsec using different version of libxml2 (binary lxml embeds its own libxml2, while xmlsec uses system one). See https://bugs.launchpad.net/lxml/+bug/2110068 Fixes: apache#52539 (cherry picked from commit 7f5c8db)
…che#53137) This is needed in order to avoid libxml and xmlsec using different version of libxml2 (binary lxml embeds its own libxml2, while xmlsec uses system one). See https://bugs.launchpad.net/lxml/+bug/2110068 Fixes: apache#52539
This is needed in order to avoid libxml and xmlsec using different version of libxml2 (binary lxml embeds its own libxml2, while xmlsec uses system one). See https://bugs.launchpad.net/lxml/+bug/2110068
Fixes: #52539
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.