Package Details: gpmdp-git 4.5.0.8.gbcd4a95-1

Git Clone URL: https://aur.archlinux.org/gpmdp-git.git (read-only)
Package Base: gpmdp-git
Description: A beautiful cross platform Desktop Player for Google Play Music.
Upstream URL: http://www.googleplaymusicdesktopplayer.com
Keywords: desktop google gpmdp music play player
Licenses: MIT
Conflicts: google-play-music-desktop-player-git, gpmdp
Provides: gpmdp
Replaces: google-play-music-desktop-player-git
Submitter: BrianAllred
Maintainer: BrianAllred
Last Packager: BrianAllred
Votes: 24
Popularity: 0.000000
First Submitted: 2016-05-30 23:57
Last Updated: 2018-02-27 20:14

Pinned Comments

BrianAllred commented on 2018-09-05 16:51

Just a heads up for new or uninformed users, git packages don't go out of date due to new releases. The latest commits are always pulled each time you build. Either build manually or use an AUR helper with proper VCS support (like yay) in order to update.

Out of date flag should only be used if something is broken.

Latest Comments

1 2 3 4 5 Next › Last »

akira commented on 2019-10-07 23:18

I got the same build error as ModYokosuka, using node v12.11.1. Using nvm to switch to node 11.15.0 allows for a successful build.

BrianAllred commented on 2019-10-07 04:19

@ModYokosuka

Do a clean checkout and try to build again. I just built it successfully without an error.

ModYokosuka commented on 2019-10-06 17:41

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:196:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.3.4-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/greg/aur/gpmdp-git/src/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/runas
gyp ERR! node -v v12.11.1
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok 
npm WARN material-ui@0.15.4 requires a peer of react-tap-event-plugin@^1.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN discord-rpc@3.1.0 requires a peer of register-scheme@github:devsnek/node-register-scheme but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ll-keyboard-hook-win@3.0.0 (node_modules/ll-keyboard-hook-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for ll-keyboard-hook-win@3.0.0: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @nodert-win10/windows.storage.streams@0.2.96 (node_modules/@nodert-win10/windows.storage.streams):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @nodert-win10/windows.storage.streams@0.2.96: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @nodert-win10/windows.media@0.2.96 (node_modules/@nodert-win10/windows.media):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @nodert-win10/windows.media@0.2.96: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @nodert-win10/windows.media.playback@0.2.96 (node_modules/@nodert-win10/windows.media.playback):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @nodert-win10/windows.media.playback@0.2.96: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @nodert-win10/windows.foundation@0.2.96 (node_modules/@nodert-win10/windows.foundation):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @nodert-win10/windows.foundation@0.2.96: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: appdmg@0.4.5 (node_modules/appdmg):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for appdmg@0.4.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mouse-forward-back@1.0.1 (node_modules/mouse-forward-back):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mouse-forward-back@1.0.1 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1


npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! runas@3.1.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the runas@3.1.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/greg/.npm/_logs/2019-10-06T17_39_04_007Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...

kjagodka commented on 2019-08-21 19:36

Can't log in. "You are trying to sign in from a browser or app that doesn't allow us to keep your account secure."

BrianAllred commented on 2018-09-05 16:51

Just a heads up for new or uninformed users, git packages don't go out of date due to new releases. The latest commits are always pulled each time you build. Either build manually or use an AUR helper with proper VCS support (like yay) in order to update.

Out of date flag should only be used if something is broken.

treeshateorcs commented on 2017-11-22 19:28

what file should I enter Last.FM API credentials in order to scrobble?

jmscaramal commented on 2017-10-02 16:20

Same problem as budkin. Updating the npm packages solved the issue here.

"sudo npm i -g npm" (updates npm globally);
"sudo npm update -g" (updates all npm packages globally)
"sudo npm install -g electron --unsafe-perm=true --allow-root" (updates electron package globally)

Hope it helps...

treeshateorcs commented on 2017-09-29 00:43

does not build


[03:39:25] Finished 'fonts' after 3.58 s
[03:39:27] Finished 'transpile' after 5.05 s
[03:39:27] Starting 'build'...
[03:39:27] Finished 'build' after 50 μs
[03:39:27] Starting 'build-release'...
[03:39:27] Finished 'build-release' after 108 ms
[03:39:27] Starting 'package:linux:64'...
Packaging app for platform linux x64 using electron v1.6.1
You are using the depreceated electron-rebuild API, please switch to using the options object instead
[03:39:46] 'package:linux:64' errored after 19 s
[03:39:46] Error: Command failed: npm prune --production
npm WARN material-ui@0.15.4 requires a peer of react-tap-event-plugin@^1.0.0 but none was installed.

npm ERR! May not delete: /tmp/electron-packager/linux-x64/Google Play Music Desktop Player-linux-x64/resources/app/node_modules/.bin

npm ERR! A complete log of this run can be found in:
npm ERR! /home/budkin/.npm/_logs/2017-09-29T00_39_46_695Z-debug.log

at ChildProcess.exithandler (child_process.js:271:12)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:927:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! google-play-music-desktop-player@4.4.1 package:linux:64: `gulp package:linux:64`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the google-play-music-desktop-player@4.4.1 package:linux:64 script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/budkin/.npm/_logs/2017-09-29T00_39_46_734Z-debug.log
==> ERROR: A failure occurred in build().
Aborting...
:: electron is now an orphan package
:: npm is now an optional package
:: failed to build gpmdp-git package(s)
pacaur -Syu gpmdp-git 164.39s user 24.18s system 54% cpu 5:48.68 total

BrianAllred commented on 2017-02-12 23:40

Sorry for falling behind on this one. I was waiting for my merge request that fixes 4.1.1 on *nix to be accepted before pushing an update that would break the app for everyone.

Should be all good now.

yubimusubi commented on 2017-01-30 22:19

The current PKGBUILD wasn't building for me - it was failing on the "npm update" line. The error code was "EBADPLATFORM" - I can provide the whole error output if it's helpful.

I was able to get it to build and install by commenting that line out (I'm not sure what it does, but that's not a step mentioned on the github page's build instructions anyway).