# Cannot get latest Version of Mopidy

**URL:** <https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004>\
**Category:** Misc\
**Created:** [May 12, 2020, 3:10pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004 "2020-05-12T15:10:29Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 3:10pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/1 "2020-05-12T15:10:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [May 12, 2020, 3:24pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/2 "2020-05-12T15:24:15Z")

</div>

Are you **sure** you have added our [apt.mopidy.com](http://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.

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 3:28pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/3 "2020-05-12T15:28:18Z")

</div>

I followed the instructions here [https://docs.mopidy.com/en/latest/installation/debian/](https://docs.mopidy.com/en/latest/installation/debian/).

I have Buster version 10

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 3:41pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/4 "2020-05-12T15:41:23Z")

</div>

These are the values in my /etc/apt/sources.list.d/mopidy.list  
deb [https://apt.mopidy.com/](https://apt.mopidy.com/) buster main contrib non-free  
deb-src [https://apt.mopidy.com/](https://apt.mopidy.com/) buster main contrib non-free

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 4:10pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/5 "2020-05-12T16:10:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [May 12, 2020, 4:11pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/6 "2020-05-12T16:11:51Z")

</div>

There are different ways to run Mopidy, more info at [https://docs.mopidy.com/en/latest/running/](https://docs.mopidy.com/en/latest/running/)

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 4:13pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/7 "2020-05-12T16:13:58Z")

</div>

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  
…

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [May 12, 2020, 4:30pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/8 "2020-05-12T16:30:07Z")

</div>

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](https://docs.mopidy.com/en/latest/troubleshooting/#show-installed-dependencies).

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 4:37pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/9 "2020-05-12T16:37:16Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 4:42pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/10 "2020-05-12T16:42:55Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 4:46pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/11 "2020-05-12T16:46:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 5:05pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/12 "2020-05-12T17:05:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [May 12, 2020, 5:05pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/13 "2020-05-12T17:05:48Z")

</div>

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/](https://mopidy.com/ext/)

---

<div class="post-metadata">

**Author:** ![Nick\_Franklin](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/nick_franklin/32/1568_2.png) [@Nick\_Franklin](https://discourse.mopidy.com/u/Nick_Franklin)\
**Post date:** [May 12, 2020, 5:07pm UTC](https://discourse.mopidy.com/t/cannot-get-latest-version-of-mopidy/4004/14 "2020-05-12T17:07:20Z")

</div>

Ah ok thanks will look at the options.
