I am trying to upgrade my Mopidy install from 2.2.3-1 to 3.0.2-1.
When I do a sudo apt upgrade I am told there is nothing to upgrade.
But when I do a sudo apt list --upgradable I get this:
mopidy/stable,stable 3.0.2-1 all [upgradable from: 2.2.3-1]
mopidy-podcast/stable,stable 3.0.0-1 all [upgradable from: 2.0.3-1]
I’m stumped…
So in reading some other threads perhaps my issue is from installing Mopidy with pip? I don’t remember doing that but it is certainly a possibility.
Output of mopidy deps
Executable: /home/bert/.local/bin/mopidy
Platform: Linux-4.4.0-116-generic-x86_64-with-Ubuntu-16.04-xenial
Python: CPython 2.7.12 from /usr/lib/python2.7
Mopidy: 2.2.3 from /usr/lib/python2.7/dist-packages
Mopidy-MusicBox-Webclient: 2.5.0 from /usr/local/lib/python2.7/dist-packages
Mopidy>=1.1.0: 2.2.3 from /usr/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy-Mopify: 1.6.1 from /usr/local/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=0.19: 2.2.3 from /usr/lib/python2.7/dist-packages
ConfigObj: 5.0.6 from /usr/local/lib/python2.7/dist-packages
six: 1.11.0 from /usr/lib/python2.7/dist-packages
Mopidy-Iris: 3.39.0 from /usr/local/lib/python2.7/dist-packages
setuptools>=3.3: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=2.0: 2.2.3 from /usr/lib/python2.7/dist-packages
Mopidy-Local-Images>=1.0: 1.0.0 from /usr/local/lib/python2.7/dist-packages
uritools>=1.0: 1.0.1 from /usr/lib/python2.7/dist-packages
ipaddress>=1.0.6: 1.0.17 from /usr/lib/python2.7/dist-packages
Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=1.1: 2.2.3 from /usr/lib/python2.7/dist-packages
ConfigObj>=5.0.6: 5.0.6 from /usr/local/lib/python2.7/dist-packages
six: 1.11.0 from /usr/lib/python2.7/dist-packages
requests>=2.0.0: 2.18.1 from /usr/lib/python2.7/dist-packages
tornado<5.0,>=3.2: 4.2.1 from /usr/lib/python2.7/dist-packages
Mopidy-Mobile: 1.9.0 from /usr/local/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=0.19: 2.2.3 from /usr/lib/python2.7/dist-packages
Mopidy-Moped: 0.7.1 from /usr/local/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=1.0.0: 2.2.3 from /usr/lib/python2.7/dist-packages
Mopidy-Local-Images: 1.0.0 from /usr/local/lib/python2.7/dist-packages
uritools>=1.0: 1.0.1 from /usr/lib/python2.7/dist-packages
ipaddress>=1.0.6: 1.0.17 from /usr/lib/python2.7/dist-packages
Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy>=1.1: 2.2.3 from /usr/lib/python2.7/dist-packages
Mopidy-Podcast: 2.0.3 from /usr/lib/python2.7/dist-packages
GStreamer: 1.8.3.0 from /usr/lib/python2.7/dist-packages/gi
Detailed information:
Python wrapper: python-gi 3.20.0
Relevant elements:
Found:
uridecodebin
souphttpsrc
appsrc
alsasink
osssink
oss4sink
pulsesink
id3demux
id3v2mux
lamemp3enc
mad
mpegaudioparse
mpg123audiodec
vorbisdec
vorbisenc
vorbisparse
oggdemux
oggmux
oggparse
flacdec
flacparse
shout2send
Not found:
flump3dec
Is there a way I can verify I installed with pip? If I did, I assume I would uninstall it with PIP uninstall mopidy?
Are you still using and trying to install on an Ubuntu 16.04 system? We definitely do not support Ubuntu 16.04.
And there’s more info at https://mopidy.com/blog/2019/12/27/mopidy-3-faq/#what-about-mopidy-3-on-ubuntu-1804-lts
Thanks for the info. Not what I wanted to read though…
I am running 18.04, I’m a bit hesitant to upgrade to Focal Fossa as this is my main server hosting my docker containers.
The only reason I was looking at upgrading was I am experiencing some audio issues with snapcast and thought upgrading to the latest Mopidy would let me use TCP Stream.
Oh right, I wrongly assumed 16.04 because
Platform: Linux-4.4.0-116-generic-x86_64-with-Ubuntu-16.04-xenial
Gstreamer 1.8.3.0 is really old now. I have almost zero experience with tcpclientsink and friends but there are plenty of bugs in the old versions of GStreamer so I wouldn’t be surprised to hear there are problems with those elements too. If you are confident with Docker then maybe you can install Mopidy into a 20.04-based container; to me that sounds way more painful than updating your system but maybe that’s just me.
Hmm that’s interesting, not sure why that’s there…
I found a VM that I had spun up as a local server for Snips before they got bought up and closed.
I’m upgrading that server to 20.04 and I’ll move Mopidy and Snapcast to that machine.
Perhaps I won’t need tcpclientsink
Got 3.0.2-1 up and running on a different VM. Things are starting to work except I can’t get any webstreams (radio) to work. They worked on my old install with the same web frontend ( [musicbox_webclient]
Network stored mp3s work great.
I did have the change the ownership for the folders in /var/lib/mopidy to mopidy:audio to be able to save the radio stations.
I’m not sure why but I am not getting anything logged so I don’t know if there is an error being thrown by mopidy in regards to the streams not playing.