From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. fa7de475fe745004b207eea07ba178b61197fe5e
Date: Wed, 12 Jun 2019 15:13:37 +0100 [thread overview]
Message-ID: <20190612141337.B807484FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2121 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 fa7de475fe745004b207eea07ba178b61197fe5e (commit)
from 5d65813aa31685e8e70b0a2e796c9abbeae60f55 (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 fa7de475fe745004b207eea07ba178b61197fe5e
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Mon Jun 10 19:02:00 2019 +0000
Tor: fix permissions after updating, too
Fixes #12088
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
Reported-by: Erik Kapfer <ummeegge(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/tor | 2 +-
src/paks/tor/install.sh | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/tor b/lfs/tor
index 1e8c3889d..d918910d4 100644
--- a/lfs/tor
+++ b/lfs/tor
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = tor
-PAK_VER = 39
+PAK_VER = 40
DEPS = "libseccomp"
diff --git a/src/paks/tor/install.sh b/src/paks/tor/install.sh
index 268bccecd..1659871b6 100644
--- a/src/paks/tor/install.sh
+++ b/src/paks/tor/install.sh
@@ -32,9 +32,10 @@ if ! getent passwd tor; then
useradd -u 119 -g tor -c "Tor daemon user" -d /var/empty -s /bin/false tor
fi
+extract_files
+restore_backup ${NAME}
+
# Adjust some folder permission for new UID/GID
chown -R tor:tor /var/lib/tor /var/ipfire/tor
-extract_files
-restore_backup ${NAME}
start_service --background ${NAME}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-12 14:13 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=20190612141337.B807484FDAF@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