@immackay can you add next line to the desktop file? This helps most WMs to recognize window.
StartupWMClass=github desktop
Git Clone URL: | https://aur.archlinux.org/github-desktop.git (read-only, click to copy) |
---|---|
Package Base: | github-desktop |
Description: | GUI for managing Git and GitHub |
Upstream URL: | https://desktop.github.com |
Keywords: | git github |
Licenses: | MIT |
Submitter: | mikelpint |
Maintainer: | alerque (shiftkey) |
Last Packager: | alerque |
Votes: | 50 |
Popularity: | 0.37 |
First Submitted: | 2017-07-22 21:26 (UTC) |
Last Updated: | 2024-11-15 19:20 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »
@immackay can you add next line to the desktop file? This helps most WMs to recognize window.
StartupWMClass=github desktop
@Eschwartz Thank you for finding that node-gyp issue.
Anyone having node-gyp issues, this should be fixed with https://bugs.archlinux.org/task/58129 but I would think everyone would have them o_O.
(If this is not using the system node-gyp, why not? Also why is python2 an undeclared makedepends.)
@xgdgsc Thanks for letting me know
@pheoxy Thanks for the information, I'll look into this, though I haven't found a way to reproduce it yet on any of my systems. The flags in makepkg.conf shouldn't affect it, no. It appears that somehow your version of node-gyp has been corrupted in some way, but that baffles me as it should download a fresh version on installation of this package (as it's a dependency in package.json).
Do you have node-gyp installed globally on your system, and if so, does it make a difference if you either remove or reinstall it?
@pheoxy how did you manage to build it finally?
python2 should be a makedep
github-desktop builds fine on latest within a virtualbox vm though. Would make flags in /etc/makepkg.conf be affecting it?
ERROR: A failure occurred in build().
On:
cd app && yarn install --force && cd .. && git submodule update --recursive --init && yarn compile:tslint
"node-gyp cannot find module"
Hope this helps I'm getting the same error as @sl1pkn07
sl1pkn07, you shouldn't have to use any sort of patch for npm to install this. If you want me to troubleshoot, you're going to have to provide more than the vague console log that yarn produces.
Why did you modify your system's electron to get rid of gnome-keyring? These are requirements to build this package. Or am I reading what you wrote correctly?
Pinned Comments
alerque commented on 2024-04-26 10:20 (UTC) (edited on 2024-04-26 10:21 (UTC) by alerque)
This package follows the Linux enabled fork releases here. Please do not flag it as OOD when the upstream Windows/OSX only Microsoft project updates but when the Linux enabled builds are available from @shiftkey. Thank you.