pirate-audio: mopidy 3.x breaks installation

@Gadgetoid @docmollo here is the PR I promised and Happy New Year! https://github.com/pimoroni/pirate-audio/pull/10

dpkg doesn’t install any dependencies, that’s up to you (or to use apt install -f). Where are you installing Gstreamer etc?

Groan. I’m not used t going to this kind of extent to side-load packages. I think this whole trick just became redundant though: https://github.com/jaedb/Iris/releases/tag/3.44.0

@rCarto Sorry for the delay…I didn’t have my Pirate Radio setup to test the work we did over the weekend, so I had to do that first. Good thing, too - it turns out the Spotify plugin, which the install.sh script installs for you, also needs to be pinned to a previous version.

So to get this working today, here are the steps I took this morning to get Spotify working. If you don’t want to use Spotify, you can check out the other Mopidy extensions and set things up to your own liking after step 6 below.

PLEASE NOTE: As of January 3, 2020 11:58 AM PST, the fix has been merged and steps 4 and 5 below are NO LONGER REQUIRED. If you performed step 1 prior to this date and time, please delete, and re-clone the repository.

1. Get Raspbian Buster setup on your Pi to your liking (network, raspi-config options etc)
2. git clone https://github.com/pimoroni/pirate-audio
3. cd pirate-audio/mopidy
4. Use your favorite editor to edit the install.sh
   1. At line 65, change/delete/comment out the apt line and replace it with:

   apt install -y --allow-downgrades mopidy=2.3.1-1 mopidy-spotify=3.1.0-0mopidy1
   apt-mark hold mopidy mopidy-spotify
   

5. Save the file
6. sudo ./install.sh (this took a while on my Pi Zero…be patient)
7. Edit /etc/mopidy/mopidy.conf and put your Spotify username and password in the section at the bottom of the file
8. Visit Mopidy-Spotify and scroll down to the Authentication section and click the green Authenticate button to allow Mopidy access to your Spotify account
9. Copy the two lines that are created into your mopidy.conf file (there are already blank placeholders in the conf file, so delete those, and copy the generated ones, or simply copy the values over).
10. Reboot the Pi

After the Pi boots, the LCD should have the UI up on it with a web URL to visit to control Mopidy. The URL takes you to the main Mopidy interface on the Pi, so to get the Spotify controls, click the Iris web client link on the page.

Migrating our Mopidy packages to Python 3/Mopidy 3.0.0 is on my TODO list.

Mopidy Raspberry GPIO at least has a pending PR: https://github.com/pimoroni/mopidy-raspberry-gpio/pull/3

Sorry I wasn’t that clear, python3-pil is/will be a dependency for the Python 3 compatible version of mopidy-pidi, nothing to do with Mopidy itself.

I’m up and running with the Mopidy 3 versions, everything seems to work great. The only install issue I hit was the following exception

Jan 26 13:30:29 raspberrypi mopidy[5265]:   File "/usr/local/lib/python3.7/dist-packages/PIL/Image.py", line 69, in <module>
Jan 26 13:30:29 raspberrypi mopidy[5265]:     from . import _imaging as core
Jan 26 13:30:29 raspberrypi mopidy[5265]: ImportError: libopenjp2.so.7: cannot open shared object file: No such file or directory

Which was solved by installing libopenjp2-7 from APT. I don’t understand why that dependency isn’t handled by python3-pil (or what the difference is between pil and pillow).

If you could bung them to me that’d be ace! I’ll get 'em hosted ASAP.

@Gadgetoid here is the list of mopidy repo packages I have on my working installation:

libspotify12-12.1.103-0mopidy1
mopidy-2.3.1-1
mopidy-spotify-3.1.0-0mopidy1
python-spotify-2.1.3-0mopidy1

I was able to fish those 4 debs out of /var/cache/apt/archives, let me know how you’d like me to deliver them. Also @Gadgetoid @docmollo @jodal, let me know if I’m missing any packages.

It sounds like Iris is very nearly ready for a Python 3 release. That being said, the other two existing Python 3 compatible webclients do certainly support selecting music. But I do admit that musicbox-webclient isn’t half as slick as Iris and clearly a lot of love went into that project.

With that mind, can we help anywhere with porting the Pirate Audio extensions? Is there a work in progress branch to continue from? Is there any questions or specific issues we can help with? I take it you’re happy to workaround that config inline comment regression.

I believe this new error is caused the combination of the Pirate Audio scripts/instructions installing specific versions from APT, which isn’t a normal thing to do from APT, and that the Mopidy project just changed our APT repo setup from using a primitive repo builder called apt-ftparchive, that never cleans out old versions, to a more advanced repo builder called reprepro, which automatically removes all but the latest version from each distribution. After this change, the only version of Mopidy available from the buster distribution on apt.mopidy.com is the latest, 3.0.1-2, which requires Python 3.

I think the best way forward for Pirate Audio is to either upgrade to Python 3 and Mopidy 3 (obviously the best approach IMHO), or to use the versions of Mopidy shipped with Debian/Raspbian. The apt.mopidy.com repo is intended for people that want to be more on the bleeding edge than the Debian distributions usually are. Currently, Pirate Audio is not up to date enough to work with the bleeding edge, and should thus stay with the Debian versions.

Is this something that warrants an upstream bug report?

Yes, I’ve finally created a new issue for it. Sorry for the delay in doing so.

@kingosticks thx for the hint to delete the file mopidy.list. That brought me one step further. But still the script did not finish successfully. I followed then the advice of @docmollo to start from scratch. Before the installation attempt I extended the partition to use the whole SD card. After that the installation script worked well. Due to the experience of the last days I consider that script as very FRAGILE. A easy way to improve the installation would be to declare minimum space requirements.

Very sorry, I was in la-la land and wrote a complete load of garbage earlier. What I should have said is since you are not finding mopidy-spotify at all (it’s not available in Debian’s repo), that sounds exactly like you do not have apt.mopidy.com added to your package sources. Which is confirmed since the mopidy.list file in question is zero bytes long.

To be totally clear, @Rocketansky, the version in the script is correct. You should remove /etc/apt/sources.list.d/mopidy.list and rerun the script.

Thanks a lot docmollo!!

Thank you for weighing in on this @docmollo - it’s very appreciated!

I will be able to give the Python 3 ports the attention they deserve when I’m back in the office- alas our Pirate Audio launch came at a somewhat awkward time!

Thank you very much @docmollo !