From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core120, updated. a554acea163fa51e0a9e5081003e4148ffdfc24b
Date: Wed, 04 Apr 2018 20:40:49 +0100 [thread overview]
Message-ID: <20180404194050.3E6511081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1669 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, core120 has been updated
via a554acea163fa51e0a9e5081003e4148ffdfc24b (commit)
from 072a19ec6419f1b18c1e4e9c98572b53a477089d (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 a554acea163fa51e0a9e5081003e4148ffdfc24b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 4 21:38:24 2018 +0200
core120: don't (re)move old packfire/gpg databases
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/120/update.sh | 6 ------
1 file changed, 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/120/update.sh b/config/rootfiles/core/120/update.sh
index 0744f3a7f..459262c86 100644
--- a/config/rootfiles/core/120/update.sh
+++ b/config/rootfiles/core/120/update.sh
@@ -74,12 +74,6 @@ fi
# Remove deprecated SSH configuration option
sed -e "/UsePrivilegeSeparation/d" -i /etc/ssh/sshd_config
-# Remove any pakfire keys stored in /
-rm -rfv /.gnupg
-
-# Move old pakfire keystore into new place
-mv -v /root/.gnupg /opt/pakfire/etc/.gnupg
-
# Import new Pakfire key
/etc/init.d/pakfire start
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-04-04 19:40 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=20180404194050.3E6511081DF2@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