Arch Linux User Repository

ector: any particular about your DNS setup, considering the "Temporary failure in name resolution"? It seems to work fine when you nmap, which is odd. (And, just to be sure, you did try the build more than once, right?)

[don@don-pc ~]$ nmap github.com -p http,git Starting Nmap 7.70 ( https://nmap.org ) at 2018-11-03 18:08 CET Nmap scan report for github.com (192.30.253.112) Host is up (0.12s latency). Other addresses for github.com (not scanned): 192.30.253.113 rDNS record for 192.30.253.112: lb-192-30-253-112-iad.github.com

PORT STATE SERVICE 80/tcp open http 8008/tcp filtered http 9418/tcp open git

Nmap done: 1 IP address (1 host up) scanned in 2.11 seconds [don@don-pc ~]$

I have no proxy, no firewall and the network works, I assure you.

I do not understand this, you could explain it to me. can you clone the repository in the error manually?

ector: seems like you're having network issues. Check out the comment to vosskaem below and make sure your network is working (can you clone the repository in the error manually?).

Unhandled rejection Error: Command failed: /usr/bin/git clone --depth=1 -q -b core-streams git://github.com/resin-io-modules/unbzip2-stream.git /home/giosue/.cache/yay/etcher/src/etcher/dist/.tmp/npm/npm-cache/_cacache/tmp/git-clone-70195241 warning: templates not found in /tmp/pacote-git-template-tmp/git-clone-e31e9b28 fatal: unable to look up github.com (port 9418) (Temporary failure in name resolution)

at ChildProcess.exithandler (child_process.js:289:12)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:970:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:257:5)

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at: npm ERR! <https://npm.community>

npm ERR! A complete log of this run can be found in: npm ERR! /home/giosue/.cache/yay/etcher/src/etcher/dist/.tmp/npm/npm-cache/_logs/2018-11-03T13_52_39_685Z-debug.log make: *** [Makefile:97: electron-develop] Error 1 ==> ERROR: A failure occurred in build(). Aborting... Error making: etcher [giosue@giosue-pc ~]$

how this error,and not install etcher npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it

Zeioth, this seems to be due to upstream's horrible build system -- I'll look into patching/submitting some issues upstream. For now, to work around that error, you can make the 'aws' command unavailable by temporarily uninstalling the package that provides it, or by building in a chroot.

Fails to install with the next error: https://i.imgur.com/pQKLVyI.png

jq is listed in makedepends. Are you experiencing any errors?

The build dependency jq is missing for the latest version