[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: Add darkhttpd.
From: |
Arun Isaac |
Subject: |
Re: [PATCH] gnu: Add darkhttpd. |
Date: |
Sat, 10 Sep 2016 18:00:38 +0530 |
User-agent: |
mu4e 0.9.16; emacs 24.5.1 |
> Why 'git-fetch'? There is a release tarball:
>
> https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2
Yes, there is a release tarball. But, there is some server side issue
with the url. When I try to download it with wget, I get a "The server
name sent was not recognized" warning. wget ignores this warning and
moves on. The guix downloader fails completely. Should the guix
downloader be patched to ignore this warning as well?
The guix downloader output is shown below.
$ guix download https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2
Starting download of /tmp/guix-file.9jzMRu
>From https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2...
ERROR: Throw to key `gnutls-error' with args `(#<gnutls-error-enum A TLS
warning alert has been received.> handshake)'.
failed to download "/tmp/guix-file.9jzMRu" from
"https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2"
guix download: error: https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2:
download failed
The wget downloader output is shown below.
$ wget https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2
--2016-09-09 23:58:53-- https://unix4lyfe.org/darkhttpd/darkhttpd-1.12.tar.bz2
Resolving unix4lyfe.org (unix4lyfe.org)... 64.62.188.248,
2001:470:1:41::403e:bcf8
Connecting to unix4lyfe.org (unix4lyfe.org)|64.62.188.248|:443... connected.
GnuTLS: A TLS warning alert has been received.
GnuTLS: received alert [112]: The server name sent was not recognized
HTTP request sent, awaiting response... 200 OK
Length: 20184 (20K) [application/x-bzip2]
Saving to: 'darkhttpd-1.12.tar.bz2'
darkhttpd-1.12.tar.bz2
100%[===========================================================>] 19.71K
39.6KB/s in 0.5s
2016-09-09 23:58:56 (39.6 KB/s) - 'darkhttpd-1.12.tar.bz2' saved [20184/20184]
I have initiated a conversation about this problem with the darkhttpd
developer. But, he has no idea what the problem might be. I'll have to
do some research on the Internet. Any ideas?
If you insist on a tarball instead of the git repo, we can add this
package after this tarball download url problem is fixed.
> I think (file-name (string-append name "-" version "-checkout")) is a
> cleaner name for a git checkout directory (but using the tarball is
> preferred).
>
> If a phase succeed, it should return non-false value, while the value of
> 'install-file' is unspecified. In such cases we add #t to the end of
> the phase. BTW I would shorten that last line by moving "/bin" to the
> next one.
Sure, I'll make these changes as well.
- [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/09
- Re: [PATCH] gnu: Add darkhttpd., Leo Famulari, 2016/09/09
- Re: [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/10
- [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/10
- Re: [PATCH] gnu: Add darkhttpd., Alex Kost, 2016/09/10
- Re: [PATCH] gnu: Add darkhttpd.,
Arun Isaac <=
- Re: [PATCH] gnu: Add darkhttpd., Alex Kost, 2016/09/10
- Re: [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/11
- [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/11
- Re: [PATCH] gnu: Add darkhttpd., Leo Famulari, 2016/09/13
- Re: [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/13
- [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/14
- Re: [PATCH] gnu: Add darkhttpd., Leo Famulari, 2016/09/14
- Re: [PATCH] gnu: Add darkhttpd., Arun Isaac, 2016/09/15
- Re: [PATCH] gnu: Add darkhttpd., Leo Famulari, 2016/09/15
- Re: [PATCH] gnu: Add darkhttpd., Ludovic Courtès, 2016/09/11