# Mismatch on Mopidy debian package version

**URL:** <https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703>\
**Category:** Misc\
**Created:** [April 26, 2015, 4:07pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703 "2015-04-26T16:07:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![morgoth](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/morgoth/32/132_2.png) [@morgoth](https://discourse.mopidy.com/u/morgoth)\
**Post date:** [April 26, 2015, 4:07pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/1 "2015-04-26T16:07:50Z")

</div>

I have mopidy installed on Ubuntu from [http://apt.mopidy.com/](http://apt.mopidy.com/)  
The 1.0.1 version was released few days ago and it looks like this version is installed on my machine: `dpkg -s mopidy => Version: 1.0.1-1` however when I run `mopidy --version => Mopidy 1.0.0`  
I’m not sure if something is messed up in my system or if there is some problem with released package.  
Any hints how to debug it?

---

<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:** [April 26, 2015, 4:24pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/2 "2015-04-26T16:24:41Z")

</div>

Can you run `which mopidy` to make sure you are running the version from APT and not some other version from pip?

---

<div class="post-metadata">

**Author:** ![morgoth](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/morgoth/32/132_2.png) [@morgoth](https://discourse.mopidy.com/u/morgoth)\
**Post date:** [April 26, 2015, 4:32pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/3 "2015-04-26T16:32:09Z")

</div>

`which mopidy => /usr/local/bin/mopidy`  
I’m starting mopidy by `/etc/init.d/mopidy start` and it uses above path:  
`ps ax | grep mopidy => /usr/bin/python /usr/local/bin/mopidy --quiet --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf:/var/lib/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:** [April 26, 2015, 4:56pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/4 "2015-04-26T16:56:22Z")

</div>

If you run `/usr/bin/mopidy --version` that’ll be Mopidy from APT and should correctly report v1.0.1. `/usr/local/bin/mopidy` is from pip, and that’s on your path before `/usr/bin/mopidy`. We used to have a problem where extensions from pip didn’t see their Mopidy dependency installed from APT and so installed another version from pip. But that should have been resolved. You should be able to safely remove the pip version.

---

<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:** [April 26, 2015, 4:57pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/5 "2015-04-26T16:57:51Z")

</div>

And there’s a better explanation here [https://docs.mopidy.com/en/latest/installation/debian/#missing-extensions](https://docs.mopidy.com/en/latest/installation/debian/#missing-extensions)

---

<div class="post-metadata">

**Author:** ![morgoth](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/morgoth/32/132_2.png) [@morgoth](https://discourse.mopidy.com/u/morgoth)\
**Post date:** [April 26, 2015, 7:38pm UTC](https://discourse.mopidy.com/t/mismatch-on-mopidy-debian-package-version/703/6 "2015-04-26T19:38:26Z")

</div>

Yes, this was exactly my problem.  
Thank you for your time.

As for the guide on uninstalling pip version, I also needed to reinstall debian package to be able to use it `sudo apt-get install --reinstall mopidy`