From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core158, updated. 23498c611f198bb7458a2db8c8abfcd572a11c91
Date: Wed, 21 Jul 2021 15:47:52 +0000 [thread overview]
Message-ID: <4GVKjN2P2gz2xpj@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1589 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, core158 has been updated
via 23498c611f198bb7458a2db8c8abfcd572a11c91 (commit)
from 131cfcf223f97a00375489f9a001a6a1dc23e972 (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 23498c611f198bb7458a2db8c8abfcd572a11c91
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jul 21 15:47:35 2021 +0000
core158: Fix any potentially broken file permissions
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/158/update.sh | 9 +++++++++
1 file changed, 9 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/158/update.sh b/config/rootfiles/core/158/update.sh
index a0e8d842f..d02b49188 100644
--- a/config/rootfiles/core/158/update.sh
+++ b/config/rootfiles/core/158/update.sh
@@ -65,6 +65,15 @@ done
# Extract files
extract_files
+# Fix permissions just in case they broke again
+chmod -v 755 \
+ /usr \
+ /usr/bin \
+ /usr/lib \
+ /usr/sbin \
+ /var \
+ /var/ipfire
+
# update linker config
ldconfig
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-21 15:47 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=4GVKjN2P2gz2xpj@people01.haj.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