Octave returning the get_forge_pkg could not read URL error

user_4999991 0
Viewed 242

Following this question on Octave's Discord channel, I tried to install the control package with

pkg install -forge control

but I get the error message

error: get_forge_pkg: could not read URL, please verify internet connection
error: called from
get_forge_pkg at line 72 column 7
get_forge_download at line 32 column 14
pkg at line 500 column 31

looking at the content of the get_forge_pkg.m script, all URLs are available within my network. I know how to download the package and install it manually, but I want to understand the problem and fix it in a canonical way.

P.S.1. This post is not a duplicate of this one, as the other page is Linux/Ubuntu/Snap specific.

P.S.2. strangely enough, trying to install the package manually using pkg install <packageName.tar.gz> I get the error:

warning: creating installation directory C:\Users\foobar~1\octave
warning: called from
    install at line 36 column 5
    pkg at line 568 column 9
octave windows
1 Answers

Line 72 there is this line downloading the package list, not the package itself.

    [html, succ] = urlread ("https://packages.octave.org/list_packages.php");

Works for me in a Chrome browser, but that redirects to https://octave.sourceforge.io/list_packages.php. Let's see what happens with curl:

[tmp] $ curl https://packages.octave.org/list_packages.php
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
[tmp] $

Looks like an expired SSL certificate on Octave's website. Please report this to the Octave maintainers at https://octave.discourse.group/.

user_1059040
Related