I'm really happy to see this, have been waiting for somebody to do that! Thank you for taking the time to update this.

This works for Mopidy-Youtube:

{ stdenv, python3Packages, mopidy }:

python3Packages.buildPythonApplication rec {
  pname = "mopidy-youtube";
  version = "3.0a1";
  
  src = python3Packages.fetchPypi {
    inherit version;
    pname = "Mopidy-YouTube";
    sha256 = "111b70x4z9ym5578jz3c327cj4l1vkfczgr4y3ggvapa5x2r7maf";
  };
  
  patchPhase = "sed s/bs4/beautifulsoup4/ -i setup.cfg";
  
  propagatedBuildInputs = [
    mopidy
    python3Packages.beautifulsoup4
    python3Packages.youtube-dl
    python3Packages.cachetools
  ];
  
  doCheck = false;
  
  meta = with stdenv.lib; {
    description = "Mopidy extension for playing music from YouTube";
    license = licenses.asl20;
    maintainers = [ maintainers.spwhitt ];
  };
}

So my uneducated guess is that there is a problem with the way beautifulsoup is packaged. Alternatively, we can submit an issue upstream asking whether bs4 is really the correct dependency name.

@GrahamcOfBorg build mopidy mopidy-gmusic mopidy-youtube mopidy-mpd mopidy-mpris mopidy-somafm

Also I believe it's better to have a separate commit for each package.

Right, these are the mopidy plugins which I didn't update (except mopidy-youtube - I can't for the life of me figure out why that's not building) - a lot of them have actually become obsolete, in the sense that they do not support the latest (python3) version of mopidy (see https://mopidy.com/ext/). Should I just remove them or would you suggest another approach? Bearing in mind python2 is now officially considered EOL now

unfortunately, you cannot have different versions of the same package in python-modules, you could try bumping that which is still compatibly with v2.0.

The other option would be to disable the other packages, however, I don't like the idea of adding packages that are already broken.

I think you might be misunderstanding me a little - mopidy has migrated to python3, and as such it does not support python2 plugins any more. The plugins which still work have been rewritten/migrated to python3. But many plugins have not been migrated, and I think that we should just remove them

needs a rebase

I think you might be misunderstanding me a little - mopidy has migrated to python3, and as such it does not support python2 plugins any more. The plugins which still work have been rewritten/migrated to python3. But many plugins have not been migrated, and I think that we should just remove them

If there's no plan to migrate the broken plugins, then please remove. Otherwise you can just mark them broken until they are in a usable state. I would just really like for package evaluation reflect the current condition of the package

At least spotify-tunigo can be marked as broken without too much thinking: upstream project is deprecated, and most features are now implemented in the mopidy-spotify plugin.

I can't figure out how to get mopidy gmusic login to work. Does anybody have any idea?

Sorry, I really let this one wither a bit - I updated, rebased, and trimmed off the bits that got merged into other PRs, so I think this ought to be good to merge now

@balsoft I just set up a new instance of mopidy, and did a mopidy gmusic login and it worked fine. Note that there's an unfortunate bug mopidy/mopidy-gmusic#231 which causes no tracks to appear when trying to select an album/artist (e.g. in ncmpcpp, pressing "2", Google Play Music -> Albums -> etc), but playing tracks from the All tracks view still works. It was fixed between the last release and master; you can use the following overlay to use the version currently on master of mopidy-gmusic instead:

self: super:
{
  mopidy-gmusic = super.mopidy-gmusic.overrideAttrs (oldAttrs: rec {
    src = self.fetchFromGitHub {
      owner = "mopidy";
      repo = "mopidy-gmusic";
      rev = "a4a78463b9765af62dd8662d45c2f8d9718f2d63";
      sha256 = "116h7v35vy0pvkab0diwfyrf8lcpbam9can8vx5cyjqxhazigzj7";
    };
  });
}

@GrahamcOfBorg build mopidy-gmusic mopidy-youtube mopidy-mpris mopidy-somafm

@NickHu oh, now it works for me too. I guess I have somehow messed up something last time I tried it ;)

@balsoft @jpotier @jonringer @FRidh Any remaining objections or should I merge this?

Can't wait for it to be merged, one more hacky overlay removed from my config!

Thank you very much for this once again!

Result of nixpkgs-review pr 78361 1