-
Notifications
You must be signed in to change notification settings - Fork 38
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
ProjectLibre failing because of SourceforgeURLProvider #67
Comments
I've been picking at this too and SourceForge have indeed restructured so that (I think) it's no longer necessary to derive the Project ID and the files RSS feed can now be found using the following URL:
... where Could the urllib2 issue be the same one that recently stung AutoPkg itself (re Github), i.e. that SourceForge now requires a newer version of TLS? If this is the case then the curl refactoring will probably be necessary. |
I'd need to see the full traceback from Python to make a better determination. Looks like we're hiding errors with exception catching. |
I've been unpicking this again recently and it is indeed related to the version of OpenSSL (and therefore TLS) running on the system, which urllib2 is leveraging. I was running AutoPkg on an older box but the issues disappeared when I migrated AutoPkg to a 10.13.6 system. Here's a quick line to check which version of TLS urllib2 is using:
( |
Yes, a big piece of the problem with SourceforgeURLProvider stay in TLS. But another in the way how Sourceforge have the adresses to the software. in a mac with 10.12 and TLS 1.0:
With burn.munki, the SourceForgeURLProvider use, i become some similar output:
But anotherwise, in a Mac with 10.14 and TLS 1.2 the ouput is better:
unfortunately with "Burn" i don´t have still success and i have this result:
Here is the problem again with these keys in burn.download.recipe: |
Getting the following when running ProjectLibre.munki (overridden):
I think this is because you're using urllib2 and sourceforge have changed to redirect the original url somewhere else. You could possibly shell out to curl and use -L/--location but I did not want to be presumptuous!
Ben
The text was updated successfully, but these errors were encountered: