From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0d6b6a219ff9dc2735f4b4b6213f9936f4a239d7
Date: Sat, 21 Oct 2017 11:20:37 +0100 [thread overview]
Message-ID: <20171021102038.1C7B11081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 0d6b6a219ff9dc2735f4b4b6213f9936f4a239d7 (commit)
from cf361ef4b55134254150b5070069f9d25b201bd1 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 0d6b6a219ff9dc2735f4b4b6213f9936f4a239d7
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Oct 21 11:20:02 2017 +0100
core115: Add missing parameter to actually generate new certificates
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/115/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/115/update.sh b/config/rootfiles/core/115/update.sh
index 61634a7..20f870d 100644
--- a/config/rootfiles/core/115/update.sh
+++ b/config/rootfiles/core/115/update.sh
@@ -50,7 +50,7 @@ ldconfig
/usr/local/bin/update-lang-cache
# generate ECDSA key on existing installations to prevent Apache from crashing
-/usr/local/bin/httpscert
+/usr/local/bin/httpscert new
# Start services
/etc/rc.d/init.d/apache2 restart
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-10-21 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171021102038.1C7B11081BCF@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox