-
Notifications
You must be signed in to change notification settings - Fork 10
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
xmlsec version issue #45
Comments
is doing I do that in my Dockerfile. I am not sure but switching back to a older version was not an option for me because i wanted to use python3.12 and i think the newest version was necessary for that |
I like configuring the python dependencies in my pipfile, and the no binary option doesn't look easy to implement in an automated fashion pypa/pipenv#5362 https://stackoverflow.com/questions/55730350/is-it-possible-to-specify-no-binary-all-in-the-pipfile. So hopefully there is a better option? |
i am sorry, i don't see another option at the moment. i had the hope that python xmlsec will release a version which works out of the box, but it looks like that's not going to happen any time soon |
Tried
OS is alma9 linux and has following installed:
|
i tried to build the almalinux docker image locally but it failed with the same error. what i observed:
since the error i have no idea how to install the newest version of xmlsec and a quick search didn't gave me any insights how to do it. sorry for not helping you more with it. |
Thank you for confirming. |
@panta-123 it is 13 not 14 that you need to pin: |
Hi all, is there a better alternative than pinning xmlsec to |
@m6121 i do a the only downside is, that it takes longer to create the docker image. i created a base-image for my build step where i put that in. |
Thanks a lot. This failed at my current base image as the xmlsec1-devel package is only |
@m6121 you could have a look to our base images: |
Thank you very much. That helps a lot! |
Package version (if known): 1.0.0
Describe the bug
I get an error
lxml & xmlsec libxml2 library version mismatch
when I use xmlsec==1.3.14 on ubuntu. Switching to xmlsec==1.3.13 resolves the issue. There is discussion here xmlsec/python-xmlsec#316, but I'm not sure on the best resolution.The text was updated successfully, but these errors were encountered: