Well, that’s not literally the response. When I do it, I get
apt update says
...
112 packages can be upgraded. Run 'apt list --upgradable' to see them.
But mpd is not one of them:
$ apt list --upgradable |grep mpd
yields nothing (indicating that apt thinks that 0.20.6-1 is the latest available). Indeed, that’s confirmed by looking at /var/lib/apt/lists/archive.volumio.org_raspbian_dists_jessie_main_binary-armhf_Packages which says
Note the keyword “local” in the response to apt list. If I understand correctly, that means that mpd was not downloaded from your apt repositories, but was a “locally-installed” package.
Note that mine is an upgrade, not a new install. Is it possible that mpd is not getting upgraded by the upgrader? That seems to be the case: the older my Volumio installation, the older the version of mpd that is installed, even though both have been “upgraded” to Volumio 2.5.26.
I had the same MPD issue with the latest Volumio (2.526) on Raspberry Pi. It turned out to be due to me having previously upgraded the entire set of packages using “sudo apt-get upgrade”. This somehow broke compatibility with the newer version of MPD included in the new Volumio release. I resolved the issue by recreating my Volumio install with the official image from the Volumio website. Everything is working well now, including Tidal playback, which I was previously having issues with.
turns out to be a complete red-herring. It does reflect the orginal version of mpd installed with the initial installation of Volumio 2.x (and differs between my RPi’s which were commissioned at different times).
But it has nothing to do with the actual version of mpd currently on the machine:
$ mpd --version
Music Player Daemon 0.20.18 (128d910-dirty)
...
My original bug report stands, though (before I got confused about what version of mpd I had). mpd 0.20.18 failed to start because of the aforementioned missing shared library. After adding an appropriate soft-link, it works fine.
Same happened to me, thanks for the solution. Updated all of my 3 devces, PI zero update to latest version went fine, but on Pi3 B+ same thing as you mentioned. No errors due updating were shown.
Cool answer. So, we are not supposed to run apt update and apt upgrade, from the archive.volumio.org repos. Why do you maintain the repos, then? For cosmetic reasons?
And don’t get me started about the security implications of your answer…
If you run service mpd status after the upgrade, most probably you’ll see that libbcm_host.so is missing. To solve this problem, you can do the following:
Compile libbcm_host.so from the open-sourced code for the ARM side libraries, found here.
First install the prerequisites for compiling the source code:
sudo apt-get install build-essential cmake
You then have to get the code from github - Interestingly, git is preinstalled (if not, just sudo apt install git)
Nice try… We host mirrors for the repositories to be good FOSS citizens and don’t add additional load on PI foundations servers. On top of that, it makes sure we have 100% availability when we build (sometimes PI repos did not work, breaking builds)
By modifying manually Volumio as you do (you’re totally free to do it, but we warn you)you will have misbehaviours and inconsistencies, so it’s not suggested
You’ve saved mine as well. Thank you. I’m running Volumio on a Pi Zero W with an Inno-Maker Raspberry Pi HiFi DAC HAT connected to a Marantz amplifier and getting music from an OpenMediaVault NAS on a Pi 4. Works well. I must admit I had done an update/upgrade on it and the problem started after a power failure.