-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | myMPD: Update install steps to avoid deprecations #3097
Comments
@jcorporation About user/group:
|
myMPD don't write files to media or download dirs. It writes only internal states to /var/lib/mympd. So it should be sufficient to add dietpi group as additional group only. The revised install script now detects old installations and run following actions:
I hope this changes enables a smooth change for the dietpi users. Feel free to propose changes to the installation / upgrade workflow for myMPD. The new version of myMPD should be released in this month. |
Great, I will implement the change to not run myMPD as dietpi group. Probably we can manage it to align DietPi release with myMPD ones so that there will be no installer incompatibilities, otherwise adjust it for this version to support both based on upstream version string. |
myMPD 5.6.0 is now released. It should not break your source build. |
@jcorporation Btw I saw: https://github.com/jcorporation/myMPD/blob/master/build.sh#L184-L188 |
+ DietPi-Software | myMPD: Update install steps to match current version: #3097 + DietPi-Software | myMPD: Do not run service as "dietpi" group. Since it only reads but not writes media files, it is sufficient with "dietpi" as supplementary group. + DietPi-Software | myMPD: Add libmediainfo0v5 to pre-reqs. It is pulled with libmediainfo-dev, but same as with libmpdclient-dev and libmpdclient2 we need to have the library stay installed if user uninstalls -dev packages, e.g. via DietPi-Cleaner. + DietPi-Software | Do not prompt via G_WHIP when Download_Install() updates a config file, but print via G_DIETPI-NOTIFY() only instead. If it is a config file where custom user changes are expected, we create a G_BACKUP_FP() anyway which as well prints related info. + DietPi-Patch | myMPD: Move systemd unit to new location (matching current release) and do not start as "dietpi" group anymore, which is only required for software titles that write media files: #3097
thanks for the hint with rmdir |
Hi,
I am the developer of myMPD and I plan to release a new myMPD release which will break your source build in the future.
The mkrelease.sh script is deprecated in my devel branch.
Please consider replacing
./mkrelease.sh
with./build.sh releaseinstall
. For now I added a./mkrelease.sh
wrapper in devel and a./build.sh
wrapper in master to prevent breakage of your source build.I see also, that you change the group of the mympd user to dietpi in your systemd service. Why is this needed and is it not better to change the primary usergroup to dietpi? Changing
usermod -a -G dietpi mympd
tousermod -g dietpi mympd
should have the same effect?In the new version myMPD creates the directory /var/lib/mympd ans it subdirs on startup with a umask of 0007.
The symlink to music/libary is no more needed. myMPD handles this internally.
Best regards and many thanks for this great software.
In the new version the configuration file is now /etc/mympd.conf no more /etc/mympd/mympd.conf. The syscmds directory is replaced with a section within mympd.conf.
The text was updated successfully, but these errors were encountered: