I encounter the same issue on Debian Trixie. Is Mopidy 4 on apt not available yet or do I have to remove Mopidy and make a fresh installation to get the newest release?
After moving the Mopidy Debian packages into Debian’s Python Team earlier this year, they have received a bit of general improvements, which I was very happy to see. I was hoping that someone else would step up and update the packages to 4.0, but that hasn’t happened yet. I’m still hoping, but not holding my breath.
If nothing happens, I’ll eventually get around to it, but my goal is for someone else to take on the maintenance of all distro packaging, as the scope of Mopidy itself is enough for the time and energy I have available for this.
As I’ve mentioned elsewhere, I’d like to contribute to Mopidy’s Debian packaging, but I’m clearly new to the Debian Python team and haven’t yet mastered its processes.
To learn the ropes, I plan to start by packaging argos (work in progress), since I’m very familiar with the code base; Once I’m comfortable with the packaging process, I’ll move on to Mopidy.
Of course, if anyone wants to speed things up, please don’t hesitate to take the lead! For my part, I’m doing this in my spare time—provided the weather is not too hot and I’m not already burnt out from spending too much time in front of a screen at work…
FWIW I have mopidy 4 running on Trixie by installing from pip. I first did a pip install but aborted before it installed dependencies - this gives you the list of dependencies.. I then carefully installed all the dependencies from apt, before pip-installing mopidy with sudo and --break-system-packages. This avoids actually breaking any system packages.
If you want to run mopidy as a service this way you’ll have to create the systemd service file yourself and possibly the /usr/local/bin/mopidy executable. I can post mine here if people are interested.
I understand, and thank you very much for all your work on Mopidy. I was just wondering whether you would recommend removing the APT version and installing the Python package instead on Debian Trixie.
Fabio
Correct me if I am wrong, but Mopidy 4.0 doesn’t bring end user new features, and there’s still work ongoing to make Mopidy-Local work as previously. So if you’re not a developer I don’t see much interest in upgrading to 4.To develop, Python packages are the way to go.