From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33861-done@debbugs.gnu.org
Subject: bug#33861: Problem building sources for guile-bash
Date: Tue, 8 Jan 2019 20:20:29 +0100 [thread overview]
Message-ID: <20190108202029.7e31b548@alma-ubu> (raw)
In-Reply-To: <87ftu3ujyv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Hi Ludo,
first of all, thanks for fixing.
On Tue, 08 Jan 2019 18:39:52 +0100
Ludovic Courtès <ludo@gnu.org> wrote:
> Hello,
>
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
>
> > Usually the git-download method should fall back to SWH, but due to
> > the 404-error it throughs an exception and never gets to the
> > fallback.
> >
> > I opened a bug for this:
> >
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33911
>
> This is now fixed so I guess we can close this bug too.
Sort of.
I tried it out: When we have a source-substitute on our server,
everything is fine.
But I tried it with network connection shut down (don't know where we
do not have substitutes and was too lazy to configure firewall): Then
it tries git, fails. It then tries our substitute server and fails. But
that failure is again a stacktrace, and it doesn't try the SWH fallback.
So, maybe it works if the substitute server returns "I don't have
something", but I don't know how to try that out (Ok, I could add a new
package). But when it has a network error, it doesn't get back to the
last fallback.
What do you think?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-01-08 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 18:00 bug#33861: Problem building sources for guile-bash Amar Singh
2018-12-24 20:33 ` Efraim Flashner
2018-12-24 21:35 ` Ricardo Wurmus
2018-12-29 18:27 ` Björn Höfling
2019-01-08 17:39 ` Ludovic Courtès
2019-01-08 19:20 ` Björn Höfling [this message]
2019-01-09 13:38 ` Ludovic Courtès
2019-01-19 6:04 ` Björn Höfling
2019-01-19 10:21 ` 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=20190108202029.7e31b548@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=33861-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).