From: "Bernhard M. Wiedemann" <bwiedemann@suse.de>
To: bug-gnulib@gnu.org
Cc: "Bernhard M. Wiedemann" <bwiedemann@suse.de>,
Bernhard Voelker <mail@bernhard-voelker.de>
Subject: [PATCH] Allow error output to be printed
Date: Mon, 7 Oct 2019 11:13:27 +0200 [thread overview]
Message-ID: <20191007091327.21338-1-bwiedemann@suse.de> (raw)
e.g. when running in a build environment without CA certificates,
wget would silently fail without giving a hint to the user
about the cause.
For background see
https://gitlab.com/gnuwget/wget2/merge_requests/450#note_226179055
It seems, -nv still shows some non-error output.
wget -q was introduced in commit feaf4df70588cf1ee30b4879a1048cc143135a67
* build-aux/bootstrap: allow wget error output to be printed
---
build-aux/bootstrap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/build-aux/bootstrap b/build-aux/bootstrap
index 5b08e7e2d..e273ea732 100755
--- a/build-aux/bootstrap
+++ b/build-aux/bootstrap
@@ -166,7 +166,7 @@ bootstrap_epilogue() { :; }
# specified directory. Fill in the first %s with the destination
# directory and the second with the domain name.
po_download_command_format=\
-"wget --mirror --level=1 -nd -q -A.po -P '%s' \
+"wget --mirror --level=1 -nd -nv -A.po -P '%s' \
https://translationproject.org/latest/%s/"
# Prefer a non-empty tarname (4th argument of AC_INIT if given), else
--
2.16.4
next reply other threads:[~2019-10-07 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 9:13 Bernhard M. Wiedemann [this message]
2019-10-07 13:00 ` [PATCH] Allow error output to be printed Tim Rühsen
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191007091327.21338-1-bwiedemann@suse.de \
--to=bwiedemann@suse.de \
--cc=bug-gnulib@gnu.org \
--cc=mail@bernhard-voelker.de \
/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.
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).