Package Details: balena-etcher 1:1.5.61-1

Git Clone URL: (read-only)
Package Base: balena-etcher
Description: Flash OS images to SD cards & USB drives, safely and easily
Upstream URL:
Licenses: Apache
Conflicts: etcher, etcher-bin, etcher-git
Submitter: gin078
Maintainer: gin078 (imrehg)
Last Packager: gin078
Votes: 172
Popularity: 2.14
First Submitted: 2019-05-13 11:35
Last Updated: 2019-11-06 13:14

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

imrehg commented on 2018-11-13 15:27

Was trying to build today:

Caching node_modules as linux-electron-2.0.12-x64-0aa3c05b71c1e672e9a7becc112c211e51d9b7bd62bbb5776851af514f4eec22.tar.gz
/tmp/yaourt-tmp-greg/aur-etcher/src/etcher/scripts/resin/electron/../shared/ line 240: AWS_ACCESS_KEY_ID: unbound variable
make: *** [Makefile:97: electron-develop] Error 1

Checking with the etcher team, and trying it out, make electron-develop -i in the build() step (add ing the -i flag) enables the package to build properly. Just checked and builds fine for me now.

ector commented on 2018-11-09 16:02

Okay today with yay I updated it. I have not done anything. Thank you

==> Creazione del pacchetto "etcher" in corso... -> Generazione del file .PKGINFO in corso... -> Generazione del file .BUILDINFO in corso... -> Creazione del file .MTREE in corso... -> Compressione del pacchetto in corso... ==> Uscita dall'ambiente di fakeroot. ==> Compilazione terminata: etcher 1.4.6-1 (ven 09 nov 2018 16:54:42 CET) ==> Pulizia in corso... [sudo] password di bob: caricamento dei pacchetti in corso... risoluzione delle dipendenze in corso... ricerca dei pacchetti in conflitto in corso...

Pacchetti (1) etcher-1.4.6-1

Dimensione totale dei pacchetti da installare: 171,31 MiB Dimensione netta dell'aggiornamento: 0,28 MiB

:: Vuoi procedere con l'installazione? [S/n] (1/1) verifica delle chiavi presenti nel porta... [----------------------] 100% (1/1) verifica dell'integrità dei pacchetti [----------------------] 100% (1/1) caricamento dei file dei pacchetti [----------------------] 100% (1/1) controllo dei conflitti in corso [----------------------] 100% (1/1) controllo dello spazio disponibile sul d... [----------------------] 100% :: Elaborazione delle modifiche al pacchetto... (1/1) aggiornamento in corso di etcher [----------------------] 100% :: Esecuzione degli hook di post-transazione... (1/3) Updating icon theme caches... (2/3) Arming ConditionNeedsUpdate... (3/3) Updating the desktop file MIME type cache... ==> Found git repo: controllo delle dipendenze in corso...

Pacchetti (2) jq-1.5-6 oniguruma-6.9.0-1

Dimensione totale dei pacchetti rimossi: 1,37 MiB

:: Vuoi rimuovere questi pacchetti? [S/n] :: Elaborazione delle modifiche al pacchetto... (1/2) rimozione in corso di jq [----------------------] 100% (2/2) rimozione in corso di oniguruma [----------------------] 100% :: Esecuzione degli hook di post-transazione... (1/1) Arming ConditionNeedsUpdate... yay -Syu 897,74s user 101,32s system 104% cpu 15:55,23 total bob@eva ~ %

ector commented on 2018-11-08 21:49

Now, I'm trying to install etcher-git,same error

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!

ector commented on 2018-11-08 21:46

yes. I have no dns use netctl default

luisnabais commented on 2018-11-06 17:19

Thanks a lot haavard, that was it. Cheers

haavard commented on 2018-11-06 10:39

luisnabais -- this is a bug in upstream's build system (issue submitted here). As a temporary workaround, you can make the aws command unavailable by uninstalling the package that provides it or building in a chroot.

luisnabais commented on 2018-11-06 10:01

/tmp/yaytmp-1000/etcher/src/etcher/scripts/resin/electron/../shared/ line 240: AWS_ACCESS_KEY_ID: unbound variable
make: *** [Makefile:97: electron-develop] Error 1
==> ERROR: A failure occurred in build().
Error making: etcher

haavard commented on 2018-11-04 12:12

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?)

ector commented on 2018-11-03 17:09

[don@don-pc ~]$ nmap -p http,git Starting Nmap 7.70 ( ) at 2018-11-03 18:08 CET Nmap scan report for ( Host is up (0.12s latency). Other addresses for (not scanned): rDNS record for

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 ~]$

ector commented on 2018-11-03 17:07

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?