From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] base-files: Mark /usr/lib/sysctl.d/10-void.conf as configuration file
Date: Thu, 13 Jun 2019 10:15:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12439@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
There is a new pull request by faulesocke against master on the void-packages repository
https://github.com/faulesocke/void-packages base-files
https://github.com/void-linux/void-packages/pull/12439
base-files: Mark /usr/lib/sysctl.d/10-void.conf as configuration file
The `10-void.conf` makes some modifications that can only be undone via rebooting, for example disabling kexec. However, I require kexec since I regularly use it on many of my servers to reboot them. If this file is not marked as a configuration file, it gets overridden on every update undoing all my changes inside. So I have to carefully check after each update, if the file got overridden before I reboot my machines. This is really annoying.
A patch file from https://github.com/void-linux/void-packages/pull/12439.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-base-files-12439.patch --]
[-- Type: application/text/x-diff, Size: 906 bytes --]
From cc18a63f8b7b30eadc97c9f75e3d8c13f4b7a6e0 Mon Sep 17 00:00:00 2001
From: Urs Schulz <voidpkgs@ursschulz.de>
Date: Thu, 13 Jun 2019 10:07:13 +0200
Subject: [PATCH] base-files: Mark /usr/lib/sysctl.d/10-void.conf as
configuration file
---
srcpkgs/base-files/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/base-files/template b/srcpkgs/base-files/template
index 9dcc5373218..78b7cc257ed 100644
--- a/srcpkgs/base-files/template
+++ b/srcpkgs/base-files/template
@@ -1,7 +1,7 @@
# Template file for 'base-files'
pkgname=base-files
version=0.140
-revision=6
+revision=7
bootstrap=yes
depends="xbps-triggers"
short_desc="Void Linux base system files"
@@ -25,7 +25,8 @@ conf_files="
/etc/group
/etc/fstab
/etc/crypttab
- /etc/nsswitch.conf"
+ /etc/nsswitch.conf
+ /usr/lib/sysctl.d/10-void.conf"
replaces="base-directories>=0"
# New system groups
next reply other threads:[~2019-06-13 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 8:15 voidlinux-github [this message]
2019-06-13 8:27 ` voidlinux-github
2019-06-13 8:40 ` voidlinux-github
2019-06-13 8:43 ` voidlinux-github
2019-06-13 8:46 ` voidlinux-github
2019-06-13 8:50 ` voidlinux-github
2019-06-13 8:52 ` voidlinux-github
2019-06-13 8:55 ` voidlinux-github
2019-06-13 9:02 ` [PR PATCH] [Closed]: " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12439@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).