[SOLVED] Moode 8.3.8 upgrade => MPD Error

[Tim Curtis]

I have the same problem. I saw some errors related to invalid parameters, basically ramp_time is not valid on V2.
Checking the filesystem in /usr/share/camilladsp/configs I can see the "old" files and the new ones named like loudness.yml.dpkg-dist, this means that a new .deb package has been installed, with newer versions of the config files, but not overwriting the old ones. Of course the .dpkg-dist files are not loaded by Camilla. The package that manages/own those config files is moode-player itself, so it seems that the upgrade of moode-player.deb did not overwrite the old config files.

Then I proceeded to go to CamillaDSP config page (Configure->CamillaDSP) and at the very bottom I clicked on `Update`, it downloaded a bunch of V2-<profile> files, and those work out of the box, but I had the new V2 files, the old broken ones and the .dpkg-dist.

I tried copying loudness.yml.dpkg-dist to loudness.yml and that indeed works, so I assume that copying the .dpkg-dist files over the file with the same name, should fix the problem.

This one liner did the job, copying the old files in filename.old and the .dpkg-dist to the profile name

for p in *.dpkg-dist; do echo $p; prof=$(basename "$p" .dpkg-dist); echo $prof; cp "$prof" "${prof}.old"; cp "$p" "${prof}";  done

And it worked, after this I just did an rm *.old to clean up and that's it, now I have the "old" profiles working and the new V2 ones too.

There are still some leftovers, old profiles that have not been updated, so are not covered by the above command. These are 

• Polarity Inversion with VC.yml
  
• Volume Control.yml
  

and those can be deleted manually.

Another possible solution would be to move away the old configs and just download the new ones, dunno enough about the differences between, for example, loudness.yml and V2-Loudness.yml, though.

I kindly suggest to the developer of moode to keep this in account and maybe release a patch that, during the installation, fixes this issue.

If you are updating by removing the package locks and doing APT upgrade to grab whatever is new in our package repo then you will end up with breakage and will need to start with a fresh image.

The only supported method of updating is via the in-place update option on System Config.