From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 296675c9ee3b984b5bfb5bdff032cdd2375639a3
Date: Sun, 12 Apr 2020 06:27:05 +0000 [thread overview]
Message-ID: <490MGx6M0Yz2y4g@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3359 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 296675c9ee3b984b5bfb5bdff032cdd2375639a3 (commit)
via b3e2c3ce269a0492e8e55208dc05dbf82977bfd4 (commit)
from f5dba19edfdbc8f925b7fced7782d7bc3c58d998 (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 296675c9ee3b984b5bfb5bdff032cdd2375639a3
Merge: b3e2c3ce2 f5dba19ed
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Apr 12 08:25:40 2020 +0200
Merge branch 'next' of git.ipfire.org:/pub/git/ipfire-2.x into next
commit b3e2c3ce269a0492e8e55208dc05dbf82977bfd4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Apr 12 08:16:28 2020 +0200
dhcpcd: update to 9.00
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/dhcpcd | 4 +---
lfs/dhcpcd | 6 +++---
2 files changed, 4 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/dhcpcd b/config/rootfiles/common/dhcpcd
index ffbe04ae4..672a47a30 100644
--- a/config/rootfiles/common/dhcpcd
+++ b/config/rootfiles/common/dhcpcd
@@ -6,12 +6,10 @@ sbin/dhcpcd
#usr/share/man/man8/dhcpcd-run-hooks.8
#usr/share/man/man8/dhcpcd.8
var/ipfire/dhcpc/dhcpcd-hooks
+#var/ipfire/dhcpc/dhcpcd-hooks/00-linux
#var/ipfire/dhcpc/dhcpcd-hooks/01-test
#var/ipfire/dhcpc/dhcpcd-hooks/02-dump
#var/ipfire/dhcpc/dhcpcd-hooks/10-mtu
-#var/ipfire/dhcpc/dhcpcd-hooks/10-wpa_supplicant
-#var/ipfire/dhcpc/dhcpcd-hooks/15-timezone
-#var/ipfire/dhcpc/dhcpcd-hooks/29-lookup-hostname
#var/ipfire/dhcpc/dhcpcd-hooks/30-hostname
#var/ipfire/dhcpc/dhcpcd-hooks/70-dhcpcd.exe
var/ipfire/dhcpc/dhcpcd-run-hooks
diff --git a/lfs/dhcpcd b/lfs/dhcpcd
index 83252e897..c9aa45b50 100644
--- a/lfs/dhcpcd
+++ b/lfs/dhcpcd
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2019 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 7.2.3
+VER = 9.0.0
THISAPP = dhcpcd-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = b7aade2cc47afa6d645f798103365402
+$(DL_FILE)_MD5 = 5360da47d4d51280dae35fe91958b63a
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-12 6:27 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=490MGx6M0Yz2y4g@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