Package Details: edex-ui 2.2.8-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: None
Last Packager: None
Votes: 13
Popularity: 0.000000
First Submitted: 2018-11-22 17:43 (UTC)
Last Updated: 2021-10-18 20:52 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

peterjin0703 commented on 2020-02-27 01:22 (UTC)

This PKGBUILD fails to me... Here is the log:

> node-pty@0.8.1 install /home/sing/.cache/yay/edex-ui/src/edex-ui-2.2.2/prebuild-src/node_modules/node-pty
> node scripts/install.js

make: entering“/home/sing/.cache/yay/edex-ui/src/edex-ui-2.2.2/prebuild-src/node_modules/node-pty/build”
  CXX(target) Release/obj.target/pty/src/unix/pty.o
g++: error: unrecognized command line option '-fno-plt'
make: *** [pty.target.mk:101：Release/obj.target/pty/src/unix/pty.o] error code 1
make: leaving“/home/sing/.cache/yay/edex-ui/src/edex-ui-2.2.2/prebuild-src/node_modules/node-pty/build”
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:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 5.5.2-1-MANJARO
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/sing/.cache/yay/edex-ui/src/edex-ui-2.2.2/prebuild-src/node_modules/node-pty
gyp ERR! node -v v10.18.1
gyp ERR! node-gyp -v v6.1.0
gyp ERR! not ok 
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-pty@0.8.1 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-pty@0.8.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/sing/.npm/_logs/2020-02-27T01_20_57_679Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! 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`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the edex-ui@2.2.2 prebuild-linux 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/sing/.npm/_logs/2020-02-27T01_20_58_030Z-debug.log

Anyone can help?

<deleted-account> commented on 2020-02-01 17:26 (UTC)

@chrisjbillington Good call - I thought it was bundled with node, turns out I was wrong. Added it to makedepends.

chrisjbillington commented on 2020-02-01 16:39 (UTC)

I don't seem to have an npm command at all - should npm be in makedepends? /usr/bin/npm is not provided by nodejs-lts-dubnium (not that I know whether it should be, I am an ignoramus about javascript/nodejs) .

/home/bilbo/.cache/yay/edex-ui/PKGBUILD: line 23: npm: command not found
==> ERROR: A failure occurred in build().
    Aborting...
Error making: edex-ui

<deleted-account> commented on 2020-02-01 15:41 (UTC)

@mcstayinskool I pushed a package update correctly linking to the latest supported Node version (LTS Dubnium) as a makedepend (commit 372d4df)

Note that if you're a Node developer you'll have to be extra careful that npm and/or node isn't aliased to some other version in your shell (disable nvm).

You might want to check out the edex-ui-git package which is some 400 commits ahead of the latest release. I currently have no ETA for when I'm going to be able to finish a new release as I missed a few deadlines already.

mcstayinskool commented on 2020-01-30 18:52 (UTC)

Broken with the identical error as @tyrannis.hawk

Not sure what you mean by using nodejs 8? Did you mean nodejs6-bin. If so, that fails to install for me due to conflicts with nodejs (which I'm loathe to uninstall because of its myriad other dependencies). If not, could you point us in the right direction?

<deleted-account> commented on 2020-01-16 15:20 (UTC)

@tyrannis.hawk Use nodejs 8.

tyrannis.hawk commented on 2020-01-16 14:55 (UTC) (edited on 2020-01-16 14:55 (UTC) by tyrannis.hawk)

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 (UTC)

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 (UTC) (edited on 2019-03-01 18:58 (UTC) by chrisjbillington)

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

<deleted-account> commented on 2019-03-01 15:13 (UTC)

@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.

« First ‹ Previous 1 2 3 Next › Last »