From: Daniel Weismueller <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] Added /var/ipfire/cups to the backup to solve the behavior discribed in bug 12404.
Date: Fri, 11 Mar 2022 10:50:56 +0100 [thread overview]
Message-ID: <20220311095056.27311-1-daniel.weismueller@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Signed-off-by: Daniel Weismueller <daniel.weismueller(a)ipfire.org>
---
lfs/cups | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lfs/cups b/lfs/cups
index 99c9c8887..5c5aef5f8 100644
--- a/lfs/cups
+++ b/lfs/cups
@@ -94,6 +94,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb
+ install -v -m 644 $(DIR_SRC)/config/backup/includes/cups \
+ /var/ipfire/backup/addons/includes/cups
+
# install initscript
$(call INSTALL_INITSCRIPT,cups)
cp -fv $(DIR_SRC)/config/cups/cupsd.conf /var/ipfire/cups/
--
2.34.1
reply other threads:[~2022-03-11 9:50 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=20220311095056.27311-1-daniel.weismueller@ipfire.org \
--to=daniel.weismueller@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