Package Details: edex-ui 2.2.2-1

Git Clone URL: https://aur.archlinux.org/edex-ui.git (read-only, click to copy)
Package Base: edex-ui
Description: A cross-platform, customizable science fiction terminal emulator with advanced monitoring & touchscreen support.
Upstream URL: https://github.com/GitSquared/edex-ui
Keywords: electron nodejs science-fiction terminal tron
Licenses: GPL3
Provides: edex-ui
Submitter: icanwalkonwater
Maintainer: GitSquared
Last Packager: GitSquared
Votes: 8
Popularity: 0.002582
First Submitted: 2018-11-22 17:43
Last Updated: 2019-05-19 17:03

Latest Comments

1 2 Next › Last »

GitSquared commented on 2020-01-16 15:20

@tyrannis.hawk Use nodejs 8.

tyrannis.hawk commented on 2020-01-16 14:55

This PKGBUILD is failing to build for me. This is the log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'prebuild-linux' ]
2 info using npm@6.13.4
3 info using node@v13.5.0
4 verbose run-script [ 'prebuild-linux' ]
5 info lifecycle edex-ui@2.2.2~prebuild-linux: edex-ui@2.2.2
6 verbose lifecycle edex-ui@2.2.2~prebuild-linux: unsafe-perm in lifecycle true
7 verbose lifecycle edex-ui@2.2.2~prebuild-linux: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/tmp/makepkg/edex-ui/src/edex-ui-2.2.2/node_modules/.bin:/usr/lib/aurutils:/home/overlord/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
8 verbose lifecycle edex-ui@2.2.2~prebuild-linux: CWD: /tmp/makepkg/edex-ui/src/edex-ui-2.2.2
9 silly lifecycle edex-ui@2.2.2~prebuild-linux: Args: [
9 silly lifecycle   '-c',
9 silly lifecycle   'rsync -a --info=progress2 src/ prebuild-src --exclude node_modules && node prebuild-minify.js && cd prebuild-src && npm install'
9 silly lifecycle ]
10 silly lifecycle edex-ui@2.2.2~prebuild-linux: Returned: code: 1  signal: null
11 info lifecycle edex-ui@2.2.2~prebuild-linux: Failed to exec prebuild-linux script
12 verbose stack Error: edex-ui@2.2.2 prebuild-linux: `rsync -a --info=progress2 src/ prebuild-src --exclude node_modules && node prebuild-minify.js && cd prebuild-src && npm install`
12 verbose stack Exit status 1
12 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
12 verbose stack     at EventEmitter.emit (events.js:305:20)
12 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
12 verbose stack     at ChildProcess.emit (events.js:305:20)
12 verbose stack     at maybeClose (internal/child_process.js:1028:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
13 verbose pkgid edex-ui@2.2.2
14 verbose cwd /tmp/makepkg/edex-ui/src/edex-ui-2.2.2
15 verbose Linux 4.19.91-1-MANJARO
16 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "prebuild-linux"
17 verbose node v13.5.0
18 verbose npm  v6.13.4
19 error code ELIFECYCLE
20 error errno 1
21 error edex-ui@2.2.2 prebuild-linux: `rsync -a --info=progress2 src/ prebuild-src --exclude node_modules && node prebuild-minify.js && cd prebuild-src && npm install`
21 error Exit status 1
22 error Failed at the edex-ui@2.2.2 prebuild-linux script.
22 error This is probably not a problem with npm. There is likely additional logging output above.
23 verbose exit [ 1, true ]

chilledfrogs commented on 2019-11-20 14:25

Hello there,

A certain command, {:timestamp=>"2019-11-20T15:19:27.744350+0100", :message=>"Process failed: /usr/bin/fish failed (exit code 127). Full command was:[\"/usr/bin/fish\", \"-c\", \"LANG=C bsdtar -czf .MTREE --format=mtree --options='!all,use-set,type,uid,gid,mode,time,size,md5,sha256,link' .INSTALL .PKGINFO usr opt\"]", :level=>:error}, always insists on using my default shell, fish, even when I start the install from a bash shell... I'm not sure how to tell it to use bash for this...

chrisjbillington commented on 2019-03-01 18:58

@GitSquared you must be right, because now it's fine.

GitSquared commented on 2019-03-01 15:13

@chrisjbillington I changed the sha256 sum on this package because the upstream tarball was changed. You might be experiencing an issue with a cache still serving the old file.

chrisjbillington commented on 2019-03-01 05:00

It is not working for me. If I download the source archive v2.1.0.tar.gz, I see that its sha256 sum is the one starting with 48d6bc, i.e. before the change you made today in 2.1.0-2.

GitSquared commented on 2019-02-28 18:02

@michaldybczak Should have been updated in AUR package version v2.1.0-2 a few minutes ago. Is it still not working?

michaldybczak commented on 2019-02-28 17:56

sha256sums isn't a match in the version from today (28.02.2019). Please, fix the sha256sums.

srei81 commented on 2019-01-31 00:16

/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/read-config-file/out/main.js:71 async function readConfig(configFile, request) { ^^^^^^^^

SyntaxError: Unexpected token function at createScript (vm.js:56:10) at Object.runInThisContext (vm.js:97:10) at Module._compile (module.js:549:28) at Object.Module._extensions..js (module.js:586:10) at Module.load (module.js:494:32) at tryModuleLoad (module.js:453:12) at Function.Module._load (module.js:445:3) at Module.require (module.js:504:17) at require (internal/module.js:20:19) at _readConfigFile (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/electron-builder/src/cli/cli.ts:10:1) at Object.args [as handler] (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/electron-builder/src/cli/cli.ts:45:5) at Object.runCommand (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/yargs/lib/command.js:238:44) at Object.parseArgs [as _parseArgs] (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/yargs/yargs.js:1089:24) at Object.get [as argv] (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/yargs/yargs.js:1004:21) at Object.<anonymous> (/tmp/pamac-build/edex-ui-git/src/edex-ui/node_modules/electron-builder/src/cli/cli.ts:19:1) at Module._compile (module.js:577:32) ==> FEHLER: Ein Fehler geschah in build().

icanwalkonwater commented on 2018-11-29 16:31

@ShayBox from what I can see, tar failed and the only reason I see right now is that one of the file in the command doesn't exists, can you manually build the package from the cache of yay with makepkg -sicCfL and give me the log file that it will have generated ?