Open gabysbrain opened 5 months ago
This has nothing to do with my commit, which has 0 rebuilds (see #233976).
For the error log, I wonder why there are -aarch64-unknown-linux-gnu
suffixes on an x86_64-linux
system. I'm not a deploy-rs
user, but it's possible that there are exotic configurations there that don't work.
I'm cross compiling for a raspberry pi target. But you are right, I just tried setting up mopidy on my local system and it worked fine. I'll have to play around with this tomorrow to see if I can isolate the problem.
Describe the bug
The mopidy service installs fine by itself but when adding any additional plugins I get a conflict error while installing. I've tried this with a few different plugins and the result is the same. The mopidy service works fine if there are no plugins listed.
Looking at the code this is probably because all extensions were updated to use the top-level
fetchPypi
but mopidy itself was not. Here's a link to the commit. I'm not sure how to fix this myself.Steps To Reproduce
Steps to reproduce the behavior:
extensionPackages
:nixos-rebuild switch
Now there should be an error about collision. In my case it's the cffi module.
Expected behavior
Extensions should be installed successfully along with the mopidy service.
Screenshots
Here is the full stack trace:
Notify maintainers
@fpletz is the mopidy maintainer but @wegank did the treewide commit
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.