public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core124, updated. 46b307324263bdf2e874701c3c5c7afc673f0eb1
Date: Sun, 23 Sep 2018 01:46:33 +0100	[thread overview]
Message-ID: <20180923004634.293361081BD3@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2798 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, core124 has been updated
       via  46b307324263bdf2e874701c3c5c7afc673f0eb1 (commit)
      from  0f2186725ef5cd62d1482b4482e20a6295ebf2ad (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 46b307324263bdf2e874701c3c5c7afc673f0eb1
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Sep 23 02:44:03 2018 +0200

    core124: fix updater
    
    fix some missing files on arm
    remove not needed rebuild initrd because we ship it already built
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/core/124/filelists/aarch64/{files => files-aarch64} | 0
 .../rootfiles/core/124/filelists/armv5tel/{files => files-armv5tel}  | 0
 config/rootfiles/core/124/update.sh                                  | 5 ++---
 3 files changed, 2 insertions(+), 3 deletions(-)
 rename config/rootfiles/core/124/filelists/aarch64/{files => files-aarch64} (100%)
 rename config/rootfiles/core/124/filelists/armv5tel/{files => files-armv5tel} (100%)

Difference in files:
diff --git a/config/rootfiles/core/124/filelists/aarch64/files b/config/rootfiles/core/124/filelists/aarch64/files-aarch64
similarity index 100%
rename from config/rootfiles/core/124/filelists/aarch64/files
rename to config/rootfiles/core/124/filelists/aarch64/files-aarch64
diff --git a/config/rootfiles/core/124/filelists/armv5tel/files b/config/rootfiles/core/124/filelists/armv5tel/files-armv5tel
similarity index 100%
rename from config/rootfiles/core/124/filelists/armv5tel/files
rename to config/rootfiles/core/124/filelists/armv5tel/files-armv5tel
diff --git a/config/rootfiles/core/124/update.sh b/config/rootfiles/core/124/update.sh
index b65bc52b8..b1b862378 100644
--- a/config/rootfiles/core/124/update.sh
+++ b/config/rootfiles/core/124/update.sh
@@ -106,16 +106,15 @@ ldconfig
 # Reload sysctl.conf
 sysctl -p
 
-# rebuild initrd to add early microcode updates
-rebuild-initrd
-
 # Remove deprecated GRUB configuration option
 if [ -e "/etc/default/grub" ]; then
 	sed -e "/^GRUB_FONT/d" -i /etc/default/grub
 fi
 
 # Update bootloader
+if [ -e /usr/bin/install-bootloader ]; then
 /usr/bin/install-bootloader
+fi
 
 # Upadate Kernel version uEnv.txt
 if [ -e /boot/uEnv.txt ]; then


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

                 reply	other threads:[~2018-09-23  0:46 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=20180923004634.293361081BD3@git01.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