# Apt v pip install for raspberrypi (raspbian)

**URL:** <https://discourse.mopidy.com/t/apt-v-pip-install-for-raspberrypi-raspbian/3360>\
**Category:** Misc\
**Created:** [July 15, 2019, 9:08am UTC](https://discourse.mopidy.com/t/apt-v-pip-install-for-raspberrypi-raspbian/3360 "2019-07-15T09:08:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vancheese](https://avatars.discourse-cdn.com/v4/letter/v/ee59a6/32.png) [@vancheese](https://discourse.mopidy.com/u/vancheese)\
**Post date:** [July 15, 2019, 9:08am UTC](https://discourse.mopidy.com/t/apt-v-pip-install-for-raspberrypi-raspbian/3360/1 "2019-07-15T09:08:15Z")

</div>

I’ve noticed that the mopidy version in the apt source([apt.mopidy.com](http://apt.mopidy.com) stretch) is now a number of updates behind the main pip release. Is this intentional? I’ve a few niggles which might have been resolved in the updates…  
Should I move over to a pip-based installation/update process or will the apt release be updated?

---

<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:** [July 15, 2019, 9:39am UTC](https://discourse.mopidy.com/t/apt-v-pip-install-for-raspberrypi-raspbian/3360/2 "2019-07-15T09:39:03Z")

</div>

Our APT repo was missing the latest version (2.2.3) but it should now be up to date.

---

<div class="post-metadata">

**Author:** ![vancheese](https://avatars.discourse-cdn.com/v4/letter/v/ee59a6/32.png) [@vancheese](https://discourse.mopidy.com/u/vancheese)\
**Post date:** [July 17, 2019, 10:29am UTC](https://discourse.mopidy.com/t/apt-v-pip-install-for-raspberrypi-raspbian/3360/3 "2019-07-17T10:29:41Z")

</div>

Awesome work - Thanks