I just installed Buster on Pi B3+ then Mopidy. I have Python 3.7 installed but when installing Mopidy I only get version 2.3.1. No matter what I try I cannot get Mopidy 3.x installed. Ive tried apt update and apt upgrade but cannot get Mopidy up update.
Are you sure you have added our apt.mopidy.com repository to your sources? v.2.3.1 is the latest version available from the Debian repository, so if that’s the latest version you see it’s likely you have not added our repository.
I followed the instructions here https://docs.mopidy.com/en/latest/installation/debian/.
I have Buster version 10
These are the values in my /etc/apt/sources.list.d/mopidy.list
deb https://apt.mopidy.com/ buster main contrib non-free
deb-src https://apt.mopidy.com/ buster main contrib non-free
Ok I might be confused here.
I have just run sudo apt install Mopidy again and it says Mopidy is already the newest version (3.0.2-1) but when I run Mopidy --version I get Mopidy 2.3.1
There are different ways to run Mopidy, more info at https://docs.mopidy.com/en/latest/running/
I understand that, but how does Mopidy --version give me 2.3.1 when apt tells me I have 3.0.2-1 installed. When I run Mopidy on the command line it tells me its version 2.3.1.
INFO Starting Mopidy 2.3.1
INFO Loading config from builtin defaults
INFO Loading config from /home/pi/.config/mopidy/mopidy.conf
…
I would guess you’ve also installed an old Python 2 version (perhaps you accidentally installed it using pip?) and that’s also on your path but I don’t know without more of the log or the output of mopidy deps.
I’m not how if that is the case. As I mentioned this is a brand new etched Buster and then I went straight to the Mopidy install page as above. Which Mopidy shows /usr/local/bin/mopidy
A search does not find any other Mopidy files
Mopidy deps
Executable: /usr/local/bin/mopidy
Platform: Linux-4.19.97-v7±armv7l-with-debian-10.4
Python: CPython 2.7.16 from /usr/lib/python2.7
Mopidy: 2.3.1 from /usr/local/lib/python2.7/dist-packages
setuptools: 40.8.0 from /usr/lib/python2.7/dist-packages
Pykka>=1.1: 2.0.2 from /usr/local/lib/python2.7/dist-packages
requests>=2.0: 2.21.0 from /usr/lib/python2.7/dist-packages
tornado<6,>=4.4: 5.1.1 from /usr/local/lib/python2.7/dist-packages
backports-abc>=0.4: 0.5 from /usr/local/lib/python2.7/dist-packages
singledispatch: 3.4.0.3 from /usr/local/lib/python2.7/dist-packages
six: 1.12.0 from /usr/lib/python2.7/dist-packages
futures: 3.3.0 from /usr/local/lib/python2.7/dist-packages
Mopidy-Moped: 0.7.1 from /usr/local/lib/python2.7/dist-packages
setuptools: 40.8.0 from /usr/lib/python2.7/dist-packages
Mopidy>=1.0.0: 2.3.1 from /usr/local/lib/python2.7/dist-packages
setuptools: 40.8.0 from /usr/lib/python2.7/dist-packages
Pykka>=1.1: 2.0.2 from /usr/local/lib/python2.7/dist-packages
requests>=2.0: 2.21.0 from /usr/lib/python2.7/dist-packages
tornado<6,>=4.4: 5.1.1 from /usr/local/lib/python2.7/dist-packages
backports-abc>=0.4: 0.5 from /usr/local/lib/python2.7/dist-packages
singledispatch: 3.4.0.3 from /usr/local/lib/python2.7/dist-packages
six: 1.12.0 from /usr/lib/python2.7/dist-packages
futures: 3.3.0 from /usr/local/lib/python2.7/dist-packages
GStreamer: 1.14.4.0 from /usr/lib/python2.7/dist-packages/gi
Detailed information:
Python wrapper: python-gi 3.30.4
Relevant elements:
Found:
uridecodebin
souphttpsrc
appsrc
alsasink
osssink
oss4sink
pulsesink
id3demux
id3v2mux
lamemp3enc
mpegaudioparse
mpg123audiodec
vorbisdec
vorbisenc
vorbisparse
oggdemux
oggmux
oggparse
flacdec
flacparse
shout2send
Not found:
flump3dec
mad
I can see from the above list it says 2.3.1 from the Phython 2.7 folder.
removing Mopidy uninstalled Mopidy 3, apt remove Mopidy again says its not installed but still runs as 2.3.1 very confused as to were 2.3.1 came from.
OK uninstalled. removed all Mopidy files from Python2, uninstall Mopidy 3 and reinstalled and that seems to have fixed it. Still don’t know where version 2.3.1 came from.
If it’s in /usr/local
then normally I’d say it came from pip. And since you have Mopidy-Moped installed I know that was installed from pip, so that’s where Mopidy 2 came from.
Note that Mopidy-Moped is not compatible with Mopidy 3. Anything that suggests installing using pip
rather than pip3
or python3 -m pip
is unlikely to be compatible. You can find a list of compatible extensions at https://mopidy.com/ext/
Ah ok thanks will look at the options.