# About documentation on installation on Debian

**URL:** <https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861>\
**Category:** Misc\
**Created:** [December 17, 2023, 9:17pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861 "2023-12-17T21:17:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [December 17, 2023, 9:17pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/1 "2023-12-17T21:17:27Z")

</div>

Just updated the Raspbian of a Raspberry PI from Bullseye to Bookworm. To install Mopidy I use [apt.mopidy.com](http://apt.mopidy.com).

Should [the documentation page on install from apt.mopidy.com](https://docs.mopidy.com/en/latest/installation/debian/#install-from-apt-mopidy-com) be updated since it mentions Bullseye, not Bookworm, even if `https://apt.mopidy.com/bookworm.list` is available?

Also, on the same page, it’s suggested that extensions not available from the package repository can be installed using `pip` but nowadays this doesn’t work straight from the box anymore; one must add the `--break-system-packages` option:

```auto
matthias@argos:~ $ sudo python3 -m pip install mopidy-bandcamp mopidy-internetarchive mopidy-listenbrainz mopidy-somafm

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

```

What would be the right way to update the documentation: Refer to `--break-system-packages` or describe how-to install a virtual environment?

---

<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:** [December 17, 2023, 9:43pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/2 "2023-12-17T21:43:53Z")

</div>

We went with --break-system-packages as per [Install from PyPI — Mopidy 4.0.0a1 documentation](https://docs.mopidy.com/en/develop/installation/pypi/) but missed that bit on the Ubuntu page and didn’t merge to the main docs yet. I think that was just an oversight, thanks for the reminder.

@jodal does that sound right?

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [January 4, 2024, 9:06pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/3 "2024-01-04T21:06:14Z")

</div>

@kingosticks Note that the `system.sh upgrade` script shipped with Iris is broken and Iris upgrade from the dedicated button in Iris is now broken. Here is the log generated after I click that button:

```auto
janv. 04 21:58:30 argos sudo[9551]: mopidy : PWD=/ ; USER=root ; COMMAND=/usr/local/lib/python3.11/dist-packages/mopidy_iris/system.sh upgrade
janv. 04 21:58:30 argos sudo[9551]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=107)
janv. 04 21:58:30 argos mopidy[9376]: INFO [Thread-15] mopidy_iris.system sudo python3 -m pip install --upgrade mopidy-iris
janv. 04 21:58:30 argos sudo[9553]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/python3 -m pip install --upgrade mopidy-iris
janv. 04 21:58:30 argos sudo[9553]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
janv. 04 21:58:34 argos mopidy[9554]: error: externally-managed-environment
janv. 04 21:58:34 argos mopidy[9554]: × This environment is externally managed
janv. 04 21:58:34 argos mopidy[9554]: ╰─> To install Python packages system-wide, try apt install
janv. 04 21:58:34 argos mopidy[9554]: python3-xyz, where xyz is the package you are trying to
janv. 04 21:58:34 argos mopidy[9554]: install.
janv. 04 21:58:34 argos mopidy[9554]:     
janv. 04 21:58:34 argos mopidy[9554]: If you wish to install a non-Debian-packaged Python package,
janv. 04 21:58:34 argos mopidy[9554]: create a virtual environment using python3 -m venv path/to/venv.
janv. 04 21:58:34 argos mopidy[9554]: Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
janv. 04 21:58:34 argos mopidy[9554]: sure you have python3-full installed.
janv. 04 21:58:34 argos mopidy[9554]:     
janv. 04 21:58:34 argos mopidy[9554]: For more information visit http://rptl.io/venv
janv. 04 21:58:34 argos mopidy[9554]: note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.

```

```auto

```

---

<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 4, 2024, 9:25pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/4 "2024-01-04T21:25:28Z")

</div>

Worth filing an issue on their repo if you can.

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [January 4, 2024, 9:40pm UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/5 "2024-01-04T21:40:12Z")

</div>

Sure. Here it is: [Upgrade button doesn't work as expected when Mopidy-Iris is served from Debian Bookworm · Issue #940 · jaedb/Iris · GitHub](https://github.com/jaedb/Iris/issues/940)

---

<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:** [July 5, 2024, 9:41am UTC](https://discourse.mopidy.com/t/about-documentation-on-installation-on-debian/5861/6 "2024-07-05T09:41:03Z")

</div>

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