From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita.karetnikov@gmail.com>
Cc: bug-guix <bug-guix@gnu.org>
Subject: Re: Check: missing signature, mirrors
Date: Wed, 05 Dec 2012 22:13:31 +0100 [thread overview]
Message-ID: <87sj7kp5hg.fsf@gnu.org> (raw)
In-Reply-To: <CAD15K4uWpLaVu6kFShY19frqC46dZdRR3H__iEvYrJkeY9oaHA@mail.gmail.com> (Nikita Karetnikov's message of "Wed, 5 Dec 2012 21:53:50 +0300")
I think there are several things going on. First, unlike me, you don’t
get redirected to a mirror where things just work.
Then there’s this:
> `http://citylan.dl.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2'...
> ERROR: Throw to key `bad-response' with args `("EOF while reading
> response body: ~a bytes of ~a" (12731 421971))'.
I can reproduce that problem, and this may well be a Guile bug related
to partial responses, which you linked to earlier.
> starting download of `guix-download.CmTclR' from
> `http://kent.dl.sourceforge.net/sourceforge/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2'...
>
> Then it hangs.
I can reproduce that one too. Here wget fails instantly with “No route
to host”, whereas (web client) is stuck like this:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (http-get (string->uri "http://kent.dl.sourceforge.net/sourceforge/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2"))
^CERROR: In procedure scm-error:
ERROR: User interrupt
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]> ,bt
In web/client.scm:
131:4 6 (http-get #<<uri> scheme: http userinfo: #f host: "kent.dl.sourceforge.net" port: #f path: "/sourceforge/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2" query: #f fragment: #f> #:port #<input-output: soc…> …)
In web/response.scm:
197:31 5 (read-response #<input-output: socket 9>)
In web/http.scm:
1116:2 4 (read-response-line #<input-output: socket 9>)
151:2 3 (read-line* #<input-output: socket 9>)
In unknown file:
2 (%read-line #<input-output: socket 9>)
In ice-9/boot-9.scm:
184:14 1 (throw system-error "fport_fill_input" "~A" ("Interrupted system call") (4))
In unknown file:
0 (scm-error signal #f "User interrupt" () (2))
--8<---------------cut here---------------end--------------->8---
I’ll look into, but you can already post these details to
bug-guile@gnu.org so we don’t lose track of it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-12-05 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 3:54 Check: missing signature, mirrors Nikita Karetnikov
2012-12-05 11:50 ` Ludovic Courtès
2012-12-05 14:58 ` Nikita Karetnikov
2012-12-05 16:45 ` Nikita Karetnikov
2012-12-05 17:02 ` Ludovic Courtès
2012-12-05 18:53 ` Nikita Karetnikov
2012-12-05 21:13 ` Ludovic Courtès [this message]
2012-12-05 21:16 ` Ludovic Courtès
2012-12-14 17:18 ` Ludovic Courtès
2012-12-16 20:28 ` Nikita Karetnikov
2012-12-16 23:19 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj7kp5hg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita.karetnikov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).