From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. eb5cd9fa57f795615e0f00c2cf2b4acf67688c7e
Date: Wed, 17 Jul 2019 16:18:12 +0100 [thread overview]
Message-ID: <20190717151812.55F5E84FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2348 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 eb5cd9fa57f795615e0f00c2cf2b4acf67688c7e (commit)
from de8810fbaa42aebf2f2a9949482fca57778db92b (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 eb5cd9fa57f795615e0f00c2cf2b4acf67688c7e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Jul 17 17:16:25 2019 +0200
pcengines-firmware: update to 4.9.0.7
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/pcengines-apu-firmware | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
Difference in files:
diff --git a/lfs/pcengines-apu-firmware b/lfs/pcengines-apu-firmware
index f318a60a6..95d9413f1 100644
--- a/lfs/pcengines-apu-firmware
+++ b/lfs/pcengines-apu-firmware
@@ -24,14 +24,14 @@
include Config
-VER = 4.9.0.3
+VER = 4.9.0.7
THISAPP = pcengines-apu-firmware-$(VER)
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = pcengines-apu-firmware
-PAK_VER = 1
+PAK_VER = 2
DEPS = "firmware-update"
@@ -52,11 +52,11 @@ apu3_v$(VER).rom = $(DL_FROM)/apu3_v$(VER).rom
apu4_v$(VER).rom = $(DL_FROM)/apu4_v$(VER).rom
apu5_v$(VER).rom = $(DL_FROM)/apu5_v$(VER).rom
-apu1_v$(VER).rom_MD5 = eb446600520f9abc3704cd806cbf160f
-apu2_v$(VER).rom_MD5 = c61e10a6b2f76c8ada4e81f9e654decd
-apu3_v$(VER).rom_MD5 = d1390d76d0ee18912825fd95b08e3f26
-apu4_v$(VER).rom_MD5 = c36cc13a1ba196b33eb85592bd44fad7
-apu5_v$(VER).rom_MD5 = da69300aed63e89e827f1e3ee3adc06d
+apu1_v$(VER).rom_MD5 = c4319969ebe031d8ab04e4d758581ca0
+apu2_v$(VER).rom_MD5 = eea6483fcd473fbb38f0547aa1aaeb31
+apu3_v$(VER).rom_MD5 = 790bc3934c7429c322d04c49e0fadb95
+apu4_v$(VER).rom_MD5 = d1c9fea737d46c82bfec2a8f3bee6c46
+apu5_v$(VER).rom_MD5 = e60502e06f5e814c2845cde447aa8f6f
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-07-17 15:18 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=20190717151812.55F5E84FDAF@people01.i.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