public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e2dce81ca343d4b55f6357417c556d63cb279f4e
Date: Tue, 30 Jan 2024 14:58:16 +0000	[thread overview]
Message-ID: <4TPSw91f8Mz2xP9@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1497 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  e2dce81ca343d4b55f6357417c556d63cb279f4e (commit)
      from  fc37ab7a5194479c551934db9e0fef115e65f0a3 (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 e2dce81ca343d4b55f6357417c556d63cb279f4e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Jan 30 14:56:11 2024 +0000

    make.sh: Build dependencies for frr
    
    These have accidentially been removed in ec01213dcf0c8283626aa9d5a7fbc30ac725ae8c.
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 make.sh | 3 +++
 1 file changed, 3 insertions(+)

Difference in files:
diff --git a/make.sh b/make.sh
index 546cdc0af..6178b46cb 100755
--- a/make.sh
+++ b/make.sh
@@ -1656,6 +1656,9 @@ buildipfire() {
   lfsmake2 dnsdist
   lfsmake2 bird
   lfsmake2 libyang
+  lfsmake2 abseil-cpp
+  lfsmake2 protobuf
+  lfsmake2 protobuf-c
   lfsmake2 frr
   lfsmake2 dmidecode
   lfsmake2 mcelog


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2024-01-30 14:58 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=4TPSw91f8Mz2xP9@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