# Rpiz2 Pypi Install not creating mopidy user?

**URL:** <https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272>\
**Category:** Misc\
**Created:** [January 1, 2022, 6:50pm UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272 "2022-01-01T18:50:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![afred](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@afred](https://discourse.mopidy.com/u/afred)\
**Post date:** [January 1, 2022, 6:50pm UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/1 "2022-01-01T18:50:53Z")

</div>

Hello, any help would be greatly appreciated.

I am trying to install Mopidy from pypi, on a rpiz2:  
Uname: Linux 5.10.63-v7+ #1488 SMP Thu Nov 18 16:14:44 GMT 2021 armv7l GNU/Linux

After install, there does not seem to be a mopidy user nor is there mopidyctl. mopidy is there and seems to start, but I usually run mopidy as service.

I started with a new sd lite, installed all dep as stated in docs. At this point I have uninstalled/installed a few times so perhaps need to nuke and pave.

Note: in the past I usually install mopidy from APT the first time then use pip to keep it and the extensions updated, but wanted to just use pip from the start this time.

[https://docs.mopidy.com/en/latest/installation/pypi/#general](https://docs.mopidy.com/en/latest/installation/pypi/#general)

```auto
$ sudo python3 -m pip install --upgrade mopidy
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting mopidy
  Using cached https://www.piwheels.org/simple/mopidy/Mopidy-3.2.0-py3-none-any.whl (127 kB)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from mopidy) (52.0.0)
Requirement already satisfied: tornado>=4.4 in /usr/local/lib/python3.9/dist-packages (from mopidy) (6.1)
Requirement already satisfied: Pykka>=2.0.1 in /usr/local/lib/python3.9/dist-packages (from mopidy) (3.0.2)
Requirement already satisfied: requests>=2.0 in /usr/lib/python3/dist-packages (from mopidy) (2.25.1)
Installing collected packages: mopidy
Successfully installed mopidy-3.2.0
 ~ $ which mopidy
/usr/local/bin/mopidy
~ $ which mopidyctl
~ $ 
<no mopidy user in passwd>

```

(ps: is there a way to get a preview before posting topic here?)

---

<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:** [January 1, 2022, 7:21pm UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/2 "2022-01-01T19:21:24Z")

</div>

You must install the Debian package to have the service setup on your system. Pypi is just Python source. [apt.mopidy.com](http://apt.mopidy.com) should have the same versions that are available on Pypi. You should use Debian packages where you can and pypi where you cannot (web clients etc).

---

<div class="post-metadata">

**Author:** ![afred](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@afred](https://discourse.mopidy.com/u/afred)\
**Post date:** [January 1, 2022, 11:13pm UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/3 "2022-01-01T23:13:58Z")

</div>

Thank you I thought that may be the problem.

I thought [apt.mopidy.com](http://apt.mopidy.com) is only buster and I am using bullseye. Will that matter?

Should I nuke and pave (create a fresh SD and install) or just install on the current pypi adulterated SD?

Thanks again!

---

<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:** [January 2, 2022, 2:17am UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/4 "2022-01-02T02:17:23Z")

</div>

It does not matter.

> Debian 10 (Buster), which also works for Raspbian Buster and Ubuntu 19.10 _and newer_.

Starting over night be less confusing as you’ll be following the suggested route but installing over the top should work OK if you’ve not messed with things.

---

<div class="post-metadata">

**Author:** ![afred](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@afred](https://discourse.mopidy.com/u/afred)\
**Post date:** [January 2, 2022, 6:24am UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/5 "2022-01-02T06:24:16Z")

</div>

Perfect!

I Uninstalled mopidy and extensions using pip.  
Then installed Mopidy on bullseye using [apt.mopidy.com/buster.list](http://apt.mopidy.com/buster.list) and it all seems to be going good.

Thanks again…

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [January 5, 2022, 6:24am UTC](https://discourse.mopidy.com/t/rpiz2-pypi-install-not-creating-mopidy-user/5272/6 "2022-01-05T06:24:22Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.