On 14/03/2017 12:29, Jeremy Henty wrote:
Pierre Labastie wrote:
On 08/03/2017 15:38, Pierre Labastie wrote:
On 08/03/2017 14:46, Richard Melville wrote:
Just tried. Works for me too, with both ftp and wget. I need to
enable passive mode with ftp. wget enables that mode
automatically.
But I do not know why we do not have the https link in the book!
I'll add it.
(This is not relevant to the original post so I changed the Subject:
line.)
Is it BLFS policy to include http links as well as ftp links? If so
then the mutt page should also include http links. (Just replace
'ftp:' with 'http:' and wget downloads the file with no problem.)
Unfortunately I can't get https links to work:
wget-1.19.1 complains:
ERROR: no certificate subject alternative name matches
requested host name ‘ftp.mutt.org’.
curl-7.53.1 complains:
curl: (51) SSL: no alternative certificate subject name matches target
host name 'ftp.mutt.org'
However this may not be a BLFS problem as I am building curl and wget
using BLFS instructions on top of a Debian Jessie system.
Regards,
Jeremy Henty
Hi Jeremy
I only meant the https link for gnutls, not for any other package, sorry
if that was not clear.
My understanding of BLFS policy is that we give an http (preferably
https if available) link and an ftp link, but only one if the other is
not available. In this case, upstream only gives the ftp link on its
download page, so it means that:
- either they have forgotten to add the http link
- or they do not want us to use the http link
- or the http link may change without notice
In this case, it seems that giving only the ftp link is what we should
do. I fo not think any of the mutt sites is accessible with https.
Regards
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
