-
Notifications
You must be signed in to change notification settings - Fork 96
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
Unable to (pip install xmlsec) since brew version 4.0.13 #254
Comments
libxmlsec1 released v1.3.0 yesterday, guessing it's related 😵💫 |
Can confirm that manually reverting to a copy of the last known good pre-1.3.0 Specific workaround steps:
References |
Here's the PR that removed soap from |
Thank you @dpritchett. Your workaround worked for me 👍 |
Hopefully #252 will be addressed soon so this can be fixed 🤞🏻 |
Per the workaround above, I had to run |
A "better" (cleaner) workaround is to create a local tap and extract the previous version, like so:
Once
Edit: This no longer works, because there were new patch versions of
And update line 4 with the correct URL: - url "https://www.aleksey.com/xmlsec/download/xmlsec1-1.2.37.tar.gz"
+ url "https://www.aleksey.com/xmlsec/download/older-releases/xmlsec1-1.2.37.tar.gz" Thanks to @karthicraghupathi for that! |
@D3X, I am facing this error when using the workaround. (I am new to MacOS) |
when you use brew 4.0.14 version, you should pay attention to brew home path is /opt/homebrew, not /usr/local/Homebrew; i also workaround it with below method;
very much thank to @dpritchett : ) |
I need one more step
|
Anxiously awaiting this update on an M1. |
Doesn't seem to work (anymore?) - it returns
Using Homebrew 4.0.24-4-g9e747d8 |
I can confirm that downgrading to libxmlsec1 1.2.37 worked. 1.3.1 broke our SAML workflow completely |
Remove the official formula> brew uninstall libxmlsec1
Uninstalling /opt/homebrew/Cellar/libxmlsec1/1.3.1_1... (220 files, 7.5MB) Download the last known good formula and shove it into
|
I got a 404 when using the wget link you provided, however the concept for this did work when I found an alternative source. Thanks a lot for pointing this out. Would have never solved this otherwise. |
@alexeocto Can you post the alternative source? |
@timothestes total brew noob over here, but I was able to give the link from the original workaround to wget and it worked. e.g.
|
I made a tap to install libxmlsec1@1.2.37
Undo:
|
You can paste this code into a file called libxmlsec1.rb and then install using formula.
|
For Windows. I couldn't find a work around hence used WSL I installed Ubuntu 22.04 on WSL and tried installing xmlsec there. But again same kind of issue. Installed brew in Ubuntu, and followed the same workaround as written in comment Now, I could install xmlsec. Hopefully, in new version these issues with different platforms will be taken care. |
Shell one liner of @amir0ff's fix. brew uninstall libxmlsec1
export DESIRED_SHA="7f35e6ede954326a10949891af2dba47bbe1fc17"
wget -O /tmp/libxmlsec1.rb "https://raw.githubusercontent.com/Homebrew/homebrew-core/${DESIRED_SHA}/Formula/libxmlsec1.rb"
brew install --formula /tmp/libxmlsec1.rb |
I am using 2,3 GHz Quad-Core Intel Core i7 with macOS 13.4.1. For me the workaround was #254 (comment) with a combination of https://stackoverflow.com/a/76639165 |
For M2 (Silicon chip) I had to run:
|
@bgaifullin I see this issue was fixed by #264, but I'm not sure how to access this fix. I see at https://pypi.org/project/xmlsec/#history that the latest release is 1.3.13 from 2022. Will there be a new release containing this fix? |
I prefer this method. However I ran into this error when I ran these commands:
The package's URL has now changed. It is present in
And make the following changes:
Once these changes are complete, you can re-run the following to complete installation:
|
It’s been a year and the issue is still not fixed on macos, requiring the user to use the abovementionned work-around |
I have this same issue. Is there any luck this would be fixed in the package without us having to resort to a workaround for MacOS? |
Same issue here. Its used in several SAML solutions, hampering
implementation of single sign on modules
Op wo 17 apr 2024 om 13:27 schreef David Z Quartz ***@***.***>
… I have this same issue. Is there any luck this would be fixed in the
package without us having to resort to a workaround for MacOS?
—
Reply to this email directly, view it on GitHub
<#254 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRXHZ6UXHSOZLLEUSRURK3Y5ZMBVAVCNFSM6AAAAAAW5S7VYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRGA2DAMRRGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This is gonna be resolved in the new version, see #284 |
All I know is that [the upstream issue looks fixed](xmlsec/python-xmlsec#254)
Hi,
I am using MacOS 13.2.1 (22D68), I didn't have any issue Installing
xmlsec
when I had brew version ~2.x.x. I've recently updated brew to version 4.0.13, and I haven't been able topip install xmlsec
since. Any idea what might this be?I have below dependencies installed
The error that I am getting
The text was updated successfully, but these errors were encountered: