From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 371661367ce0b00cce45b49f1d242a74978261e0
Date: Fri, 29 May 2020 10:28:31 +0000 [thread overview]
Message-ID: <49YLPq5Wmqz2xd6@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1504 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 371661367ce0b00cce45b49f1d242a74978261e0 (commit)
from fead20a917dfdb8d7e091f8a8c6e39625ea9e315 (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 371661367ce0b00cce45b49f1d242a74978261e0
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu May 28 19:00:47 2020 +0000
netatalk: Add krb5 as a dependency
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/netatalk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/netatalk b/lfs/netatalk
index 09107e2e8..16fd292eb 100644
--- a/lfs/netatalk
+++ b/lfs/netatalk
@@ -32,9 +32,9 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = netatalk
-PAK_VER = 1
+PAK_VER = 2
-DEPS = avahi dbus
+DEPS = avahi dbus krb5
CFLAGS += -Wno-unused-result
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-05-29 10:28 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=49YLPq5Wmqz2xd6@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