apple-music-electron: 1.5.2 -> 1.5.5

[IvarWithoutBones]

Motivation for this change

Fails with the following error without the change in pkgs/build-support/appimage/default.nix:

/nix/store/48a25nl0bpcya9pdajcwxdx4k9cjfzgr-Apple.Music-1.5.5-extracted/apple-music-electron: error while loading shared libraries: libxshmfence.so.1: cannot open shared object file: No such file or directory

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[SuperSandro2000]

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 116012 run on x86_64-linux 1

1 package blacklisted:

• appimage-run-tests

36 packages built:

• Sylk
• anki-bin
• appimage-run
• apple-music-electron
• chrysalis
• deltachat-electron
• devdocs-desktop
• electronplayer
• irccloud
• joplin-desktop
• keeweb
• ledger-live-desktop
• lens
• lunar-client
• marktext
• minetime
• molotov
• mycrypto
• notable
• nuclear
• p3x-onenote
• plexamp
• radicle-upstream
• rambox
• rambox-pro
• runwayml
• ssb-patchwork
• standardnotes
• station
• timeular
• trezor-suite
• tusk
• unityhub
• wootility
• zettlr
• zulip

[IvarWithoutBones]

/marvin opt-in
/status needs_reviewer

[marvin-mk2]

Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here.

[kevincox]

Can you explain why the source was changed? I feel somewhat uncomfortable with approving the source change with no context. I think the commit description should include information on this new source.

[kevincox]

Also should the homepage be updated to the new source?

[IvarWithoutBones]

@kevincox The old source now simply redirects to this one, I think the owner of the repository changed their account name. I'll put that in the commit description.

As for the homepage, you're right! I'll change that, good catch :)

[kevincox]

Sounds good. I would still include that information in the commit message just to make it clear that this is the same source but it has been moved. It makes it easier for anyone else reading the commits to see what happened.