live check fetch failures

[Ryan Schmidt]

On Jun 19, 2021, at 05:12, Christopher Jones wrote:

> Hi,
> 
> I’ve been noticing recently a number of ports are failing to live check, with errors like
> 
>> port -d live libogg                               
> DEBUG: Changing to port directory: /Users/chris/Projects/MacPorts/ports/multimedia/libogg
> DEBUG: OS darwin/20.5.0 (macOS 11.4) arch i386
> DEBUG: adding the default universal variant
> DEBUG: Reading variant descriptions from /Users/chris/Projects/MacPorts/ports/_resources/port1.0/variant_descriptions.conf
> DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies
> DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies
> DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies
> DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies
> DEBUG: Running callback portstartupitem::add_notes
> DEBUG: Finished running callback portstartupitem::add_notes
> DEBUG: Logging disabled, error opening log file: can't create directory "/opt/local/var/macports/logs/_Users_chris_Projects_MacPorts_ports_multimedia_libogg": permission denied
> DEBUG: Executing org.macports.main (libogg)
> DEBUG: livecheck phase started at Sat Jun 19 11:10:30 BST 2021
> DEBUG: Executing org.macports.livecheck (libogg)
> DEBUG: Port (livecheck) version is 1.3.4
> DEBUG: Loading the defaults from '/Users/chris/Projects/MacPorts/ports/_resources/port1.0/livecheck/fallback.tcl'
> DEBUG: Fetching https://downloads.xiph.org/releases/ogg/
> DEBUG: Using CURL options --append-http-header {Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8} --enable-compression
> Error: cannot check if libogg was updated (error:1400442E:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert protocol version)
> 
> A quick web search suggests this could be an issue with an older version of (lib)curl being used ? Does anyone have any insights into this ?

If you're seeing that on macOS 11, then my interpretation is that whatever security settings are being employed by that web server are too restrictive to be realistic, and I would suggest you contact the administrator of the server and ask them to be more permissive with whatever they're doing.