From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6158761b2f81a08f115f5b614ad29fdc4bd210cf
Date: Fri, 10 May 2024 10:44:12 +0000 [thread overview]
Message-ID: <4VbQVN6yDKz2xQZ@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 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 6158761b2f81a08f115f5b614ad29fdc4bd210cf (commit)
from 1330e280de8759cf05193031293900ed0512b94b (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 6158761b2f81a08f115f5b614ad29fdc4bd210cf
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri May 10 12:42:29 2024 +0200
mympd: remove create config start
this now resets an existing option like the port to
default.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/paks/mympd/install.sh | 2 --
1 file changed, 2 deletions(-)
Difference in files:
diff --git a/src/paks/mympd/install.sh b/src/paks/mympd/install.sh
index 9c154b5b4..9351ccaef 100644
--- a/src/paks/mympd/install.sh
+++ b/src/paks/mympd/install.sh
@@ -27,8 +27,6 @@ ln -svf /etc/init.d/mympd /etc/rc.d/rc3.d/S66mympd
ln -svf /etc/init.d/mympd /etc/rc.d/rc0.d/K34mympd
ln -svf /etc/init.d/mympd /etc/rc.d/rc6.d/K34mympd
restore_backup ${NAME}
-# create/check config
-/usr/bin/mympd -u nobody -c
# start services
/etc/init.d/mpd restart
/etc/init.d/mympd start
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-05-10 10:44 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=4VbQVN6yDKz2xQZ@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