From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 2/6] Core Update 157: Ship backup package to apply changed permissions
Date: Fri, 21 May 2021 15:41:05 +0200 [thread overview]
Message-ID: <b1e8a1b5-7937-9de7-8f14-f12ffa076f12@ipfire.org> (raw)
In-Reply-To: <429b9a37-26f3-5ec4-d82d-99cb4aaa27a7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
This is required as "backup" itself does not gets updated automatically,
contrary to it's LFS file suggesting by having a "PAK_VER" number.
In order to fix #12619, it is therefore necessary to ship the backup
files with Core Update 157.
Partially fixes: #12619
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/rootfiles/core/157/filelists/backup | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/157/filelists/backup
diff --git a/config/rootfiles/core/157/filelists/backup b/config/rootfiles/core/157/filelists/backup
new file mode 120000
index 000000000..38e28a8b4
--- /dev/null
+++ b/config/rootfiles/core/157/filelists/backup
@@ -0,0 +1 @@
+../../../common/backup
\ No newline at end of file
--
2.26.2
next prev parent reply other threads:[~2021-05-21 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 13:40 [PATCH 0/6] Patchset for fixing errors surfaced in Core Update 157 (testing) Peter Müller
2021-05-21 13:40 ` [PATCH 1/6] Core Update 157: Apply changed SSH configurations Peter Müller
2021-05-21 13:41 ` Peter Müller [this message]
2021-05-21 13:41 ` [PATCH 3/6] pppd: Explicitly ship pppd shared object files Peter Müller
2021-05-21 13:41 ` [PATCH 4/6] Core Update 157: Delete shared object files leftover from pppd 2.4.8 Peter Müller
2021-05-21 13:42 ` [PATCH 5/6] nagios-plugins: Set SUID bit for plugins which need it to function properly Peter Müller
2021-05-21 13:42 ` [PATCH 6/6] Icinga: Do not ship event handlers for Nagios Peter Müller
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=b1e8a1b5-7937-9de7-8f14-f12ffa076f12@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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