Re: pkg install -forge issues?

[Mike Miller]

On Fri, Dec 16, 2016 at 12:44:49 -0500, Nicholas Jankowski wrote:
> On Fri, Dec 16, 2016 at 12:18 PM, Mike Miller <address@hidden> wrote:
> > Does this work
> >
> >   [txt, status] = urlread ("http://packages.octave.org/gsl/index.html";)
> >
> >
> >>  [txt, status] = urlread ("http://packages.octave.org/gsl/index.html";)
> txt =
> status = 0
> 
> 
> ? Does it work in your web browser of choice?
> >
> >
> going to
> http://packages.octave.org/gsl/index.html
> 
> redirects to
> 
> https://octave.sourceforge.io/gsl/index.html
> 
> which loads fine.
> 
> 
> 
> > Is the Windows distribution unable to cope with the sourceforge ssl
> > certs?
> >
> don't think so.  have no problem manually downloading the package which is
> pulling from https://sourceforge.net

I meant the Windows distribution of Octave, not the Windows OS in
general.

The error with urlread seems to confirm that it can't read the URL, but
without any details about why. I'm only guessing this is because of the
ssl certs. Can you successfully read http URLs but not any https URLs,
taking redirects into account?

Here's a sample set of http URLs that do not automatically redirect to
https

  urlread ("http://www.gnu.org/";)
  urlread ("http://www.debian.org/";)
  urlread ("http://www.google.com/";)

Do these work for you? Do they work with https?

And circling back to sourceforge, does this URL work

  urlread ("http://mingw.sourceforge.net/";)

versus this one

  urlread ("http://octave.sourceforge.net/";)

Does the Octave bin directory include the curl executable? Can you try
any failing URLs with "curl -v" and see if any errors or other details
can help indicate what the problem is?

-- 
mike