public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e7ea357cecf5e069dd4fb4e5cd6099d8e5b7d9a4
Date: Tue, 20 Mar 2018 11:10:39 +0000	[thread overview]
Message-ID: <20180320111039.8D8FE1081DF2@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1937 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  e7ea357cecf5e069dd4fb4e5cd6099d8e5b7d9a4 (commit)
      from  42deeb3b450c74138dfb76d9d45d4588a5271887 (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 e7ea357cecf5e069dd4fb4e5cd6099d8e5b7d9a4
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Mar 20 11:08:58 2018 +0000

    Forgot to "git add" the new pakfire init script
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 src/initscripts/system/{network-trigger => pakfire} | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
 copy src/initscripts/system/{network-trigger => pakfire} (55%)

Difference in files:
diff --git a/src/initscripts/system/pakfire b/src/initscripts/system/pakfire
new file mode 100644
index 000000000..1238833d5
--- /dev/null
+++ b/src/initscripts/system/pakfire
@@ -0,0 +1,25 @@
+#!/bin/sh
+########################################################################
+# Begin $rc_base/init.d/pakfire
+#
+# Description : Imports the keyring to make Pakfire operational
+#
+########################################################################
+
+. /etc/sysconfig/rc
+. ${rc_functions}
+
+case "${1}" in
+	start)
+		boot_mesg "Setting up Pakfire Package Manager..."
+		gpg --import /opt/pakfire/pakfire.key &>/dev/null
+		evaluate_retval
+		;;
+
+	*)
+		echo "Usage: ${0} {start}"
+		exit 1
+		;;
+esac
+
+# End $rc_base/init.d/pakfire


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

                 reply	other threads:[~2018-03-20 11:10 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=20180320111039.8D8FE1081DF2@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