From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 09b09b859df6ee460acb28a0c7d5d6a0dfa42a60
Date: Sat, 15 Feb 2020 16:52:58 +0000 [thread overview]
Message-ID: <48KbsR0yS8z2y32@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1647 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 09b09b859df6ee460acb28a0c7d5d6a0dfa42a60 (commit)
from 900652ec6ce9d8d2e58225fa8abbfddbfdcbc05f (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 09b09b859df6ee460acb28a0c7d5d6a0dfa42a60
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sat Feb 15 16:21:04 2020 +0100
make.sh: Build lua before haproxy.
In commit b6ab15eaa2a899944c7edca99769fa4469f215d3 lua support
for haproxy has been enabled, so lua now has to be compiled before
haproxy.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 277ac8633..c0137ecc0 100755
--- a/make.sh
+++ b/make.sh
@@ -1618,9 +1618,9 @@ buildipfire() {
lfsmake2 pigz
lfsmake2 tmux
lfsmake2 perl-Text-CSV_XS
+ lfsmake2 lua
lfsmake2 haproxy
lfsmake2 ipset
- lfsmake2 lua
lfsmake2 dnsdist
lfsmake2 bird
lfsmake2 frr
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-02-15 16:52 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=48KbsR0yS8z2y32@people01.haj.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