Package Details: balena-etcher 2:1.7.9-1

Git Clone URL: https://aur.archlinux.org/balena-etcher.git (read-only, click to copy)
Package Base: balena-etcher
Description: Flash OS images to SD cards & USB drives, safely and easily
Upstream URL: https://balena.io/etcher
Licenses: Apache
Conflicts: etcher, etcher-bin, etcher-git
Submitter: gin078
Maintainer: zhullyb (Clansty, sukanka)
Last Packager: zhullyb
Votes: 242
Popularity: 2.21
First Submitted: 2019-05-13 11:35 (UTC)
Last Updated: 2022-04-22 21:12 (UTC)

Latest Comments

neoarch666 commented on 2022-04-09 12:58 (UTC) (edited on 2022-04-09 13:58 (UTC) by neoarch666)

Hello my problem of compil Balnela-etcher resolve when i install all dependency (optionally) of electon12 (i using pamac-aur or pamac-gtk app for see it) the name of dependency is "trash-cli" and "kde-cli-tools" but i think is just trash-cli missing and i must instaled it

yurikoles commented on 2022-02-21 16:14 (UTC)

@zhullyb @Clansty

balena-etcher and etcher-git no longer in conflict, please update your package accordingly.

arsh commented on 2022-02-03 21:15 (UTC)

The nodejs conflict K4LCIFER mentioned is still persistant.

darkbasic commented on 2022-01-19 21:58 (UTC)

Would it be possible to fix the epoch please?

Der_Chefkoch commented on 2021-12-30 23:31 (UTC)

There's issue with the epochs of this package as discussed here:

https://bbs.archlinux.org/viewtopic.php?pid=2012431#p2012431

cmsigler commented on 2021-12-18 01:58 (UTC)

Hi,

PKGBUILD and .SRCINFO are not in sync. .SRCINFO specifies nodejs<17 but PKGBUILD doesn't(?). I gather this is intentional but it is, um... "bad form" IIUC.

Hope this is of some help :) Cheers!

Clemmitt Sigler

7314776 commented on 2021-12-01 20:49 (UTC) (edited on 2021-12-04 17:09 (UTC) by 7314776)

Clean chroot build failed with the same outcome (see openssl_fips below) P.S. As of December 04, 2021, switched to etcher-bin that provides the same functionality but deb-package is used as source.

yochananmarqos commented on 2021-11-30 00:19 (UTC)

This is where nvm comes into play. See Nodejs package guidelines. Upstream uses Node 14.

K4LCIFER commented on 2021-11-29 23:14 (UTC)

nodejs conflict:

:: There are 3 providers available for nodejs<17:
:: Repositorycommunity
    1) nodejs-lts-erbium 2) nodejs-lts-fermium 3) nodejs-lts-gallium

Picking one of these options will result in

:: nodejs-lts-erbium and nodejs are in conflict.

As such, one cannot update, nor install.

Wild_Penguin commented on 2021-11-29 10:26 (UTC)

Seems to break because of openssl_fips not defined error. A more concise log snippet:

    npm ERR! path /home/ville/.cache/aurutils/sync/balena-etcher/src/etcher/node_modules/@ronomon/direct-io
    npm ERR! command failed
    npm ERR! command sh -c node-gyp rebuild
    npm ERR! gyp info it worked if it ends with ok
    npm ERR! gyp info using node-gyp@8.2.0
    npm ERR! gyp info using node@17.1.0 | linux | x64
    npm ERR! gyp info find Python using Python version 3.9.9 found at "/usr/bin/python3"
    npm ERR! gyp info spawn /usr/bin/python3
    npm ERR! gyp info spawn args [
    npm ERR! gyp info spawn args   '/usr/lib/node_modules/node-gyp/gyp/gyp_main.py',
    npm ERR! gyp info spawn args   'binding.gyp',
    npm ERR! gyp info spawn args   '-f',
    npm ERR! gyp info spawn args   'make',
    npm ERR! gyp info spawn args   '-I',
    npm ERR! gyp info spawn args   '/home/ville/.cache/aurutils/sync/balena-etcher/src/etcher/node_modules/@ronomon/direct-io/build/config.gypi',
    npm ERR! gyp info spawn args   '-I',
    npm ERR! gyp info spawn args   '/usr/lib/node_modules/node-gyp/addon.gypi',
    npm ERR! gyp info spawn args   '-I',
    npm ERR! gyp info spawn args   '/home/ville/.electron-gyp/12.0.2/include/node/common.gypi',
    npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
    npm ERR! gyp info spawn args   '-Dvisibility=default',
    npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/ville/.electron-gyp/12.0.2',
    npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/node-gyp',
    npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/ville/.electron-gyp/12.0.2/<(target_arch)/node.lib',
    npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/ville/.cache/aurutils/sync/balena-etcher/src/etcher/node_modules/@ronomon/direct-io',
    npm ERR! gyp info spawn args   '-Dnode_engine=v8',
    npm ERR! gyp info spawn args   '--depth=.',
    npm ERR! gyp info spawn args   '--no-parallel',
    npm ERR! gyp info spawn args   '--generator-output',
    npm ERR! gyp info spawn args   'build',
    npm ERR! gyp info spawn args   '-Goutput_dir=.'
    npm ERR! gyp info spawn args ]
    npm ERR! gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
    npm ERR! gyp ERR! configure error 
    npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
    npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/node-gyp/lib/configure.js:353:16)
    npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
    npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
    npm ERR! gyp ERR! System Linux 5.15.4-zen1-1-zen
    npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
    npm ERR! gyp ERR! cwd /home/ville/.cache/aurutils/sync/balena-etcher/src/etcher/node_modules/@ronomon/direct-io
    npm ERR! gyp ERR! node -v v17.1.0
    npm ERR! gyp ERR! node-gyp -v v8.2.0
    npm ERR! gyp ERR! not ok

depletedKnowledg commented on 2021-11-24 17:37 (UTC)

Has a problem retrieving dependence:

error: failed retrieving file 'electron12-12.2.3-1-x86_64.pkg.tar.zst' from arch.mirror.constant.com : The requested URL returned error: 404

-> electron12 not satisfied, flushing install queue

Breaks on npm after that, can comment log if necessary

K4LCIFER commented on 2021-11-07 23:05 (UTC)

Thank you @zhullyb for adopting, and fixing this package! It is greatly appreciated.

zuzavo commented on 2021-11-07 13:35 (UTC)

Now you can download an appimage from their website ready to work without any installation. The only requisite is to install previously the "libappimage" package from the extra repository.

mvk commented on 2021-10-06 01:04 (UTC)

White screen - not usable.

NoahRR commented on 2021-09-23 01:22 (UTC)

White Screen - not usable.

zeroconf commented on 2021-09-19 19:24 (UTC)

Please update, there is already newer version out - https://www.balena.io/etcher/

K4LCIFER commented on 2021-09-10 00:39 (UTC)

White screen. App unuseable.

Spixmaster commented on 2021-09-07 10:05 (UTC) (edited on 2021-09-07 10:11 (UTC) by Spixmaster)

@maintainer This package is not usable for over a month now nor is it up to date. Could you at least give a response or is this package orphaned?

jfabernathy commented on 2021-08-24 18:24 (UTC)

Same White screen for me on a fresh install.

archnoon commented on 2021-08-23 15:04 (UTC)

I report the same... White screen and no messages when executing in the terminal.

luckylj82 commented on 2021-08-15 18:46 (UTC)

Agree with Spixmaster, I can not get anything more than a white screen with the latest version.

Spixmaster commented on 2021-08-05 17:46 (UTC) (edited on 2021-08-05 19:39 (UTC) by Spixmaster)

The software is unusable. The window only displays a white screen with version 2:1.5.121-1.

Serial commented on 2021-07-15 10:55 (UTC)

@yurikoles

In Version etcher-bin is working normally.

Thank you very much

yurikoles commented on 2021-07-15 08:48 (UTC)

@Serial

Please try to reproduce on official build, etcher-bin

Serial commented on 2021-07-13 18:47 (UTC)

Hey guys

Balena-etcher 2:1.5.120-1 in EndeavorOS flavor Gnome 40 does not show its image after it is opened, see application image link below. Any suggestion? Just wait for new update?

https://imgur.com/Vq7kA1L

chrisstm commented on 2021-04-13 18:40 (UTC)

@hotfloppy,

thnx m8

hotfloppy commented on 2021-04-09 11:23 (UTC) (edited on 2021-04-09 11:24 (UTC) by hotfloppy)

@chrisstm,

I assumed you come from Manjaro? If yes, you can use electron package from Arch temporarily, at least until version 12 of electron landed in Manjaro's repo.

$ cd /tmp # optional
$ wget --content-disposition 'https://archlinux.org/packages/community/x86_64/electron/download/'
$ sudo pacman -U electron*.zst

And proceed to install/update balena-etcher.

chrisstm commented on 2021-04-09 05:25 (UTC)

Hi.

I get "unable to satisfy dependency 'electron>=12.0.0' required by balena-etcher".

Thnx in advance.

cmsigler commented on 2021-03-23 16:28 (UTC)

@SalmonMolon,

Thank you for your report, your solution WFM :)

Clemmitt

Spixmaster commented on 2021-03-23 09:04 (UTC)

@sl13kp For me, it does not.

sl13kp commented on 2021-03-21 03:16 (UTC) (edited on 2021-03-22 12:33 (UTC) by sl13kp)

With electron9-bin it works fine thanks again. (micwoj92)

truita commented on 2021-03-20 11:32 (UTC)

Removing or commenting out export NPM_VERSION=$(npm --version) in the PKGBUILD fixed building for me.

gin078 commented on 2021-03-18 13:10 (UTC)

Hi all, thanks for the reports of your failing builds. I'm working on getting this package back functional.

cmsigler commented on 2021-03-18 11:18 (UTC) (edited on 2021-03-18 11:22 (UTC) by cmsigler)

Hi again,

Perusing the github for balena-io/etcher it appears v1.5.117 is in development, and its electron dependency will be upgraded to ver. 11. Last activity on branch electron-11-build-e446afec... is 3 days ago (2021-03-15). One might speculate that build issues will be fixed when the new version is released??? Of course, electron v12 was released on March 1 with a patchlevel on March 10, so it's a never-ending target to chase....

I thought about creating a balena-etcher-bin AUR pkg from the .deb pkg provided on https://deb.etcher.io/ but I rarely use it so I am unlikely to maintain it properly :\ Anyone else interested? :)

HTH.

Clemmitt Sigler

P.S.: .deb pkgs seem to be out of date anyway, latest I found was 1.5.100 :(

cmsigler commented on 2021-03-17 21:31 (UTC) (edited on 2021-03-17 21:37 (UTC) by cmsigler)

Hi,

As reported by Spixmaster, I can't get this to build, either. I have electron9-bin installed but I suspect that doesn't make a difference. Am I wrong on that?...

I used yay and did a cleanBuild, so no leftover crud. Build error output:

================

==> Starting build()...

./scripts/resin/electron/install.sh \

-b /home/blah/.cache/yay/balena-etcher/src/etcher \

-r x64 \

-s linux \

-m 7.6.3

node: v15.11.0

npm: 7.6.3

...

...

...

target = "9.4.1"

; "cli" config from command line options

long = true

omit = []

user-agent = "npm/7.6.3 node/v15.11.0 linux x64"

Installing dependencies

Need to install the following packages:

npm@7.6.3

Ok to proceed? (y) y

added 1545 packages, and audited 1546 packages in 5m

16 vulnerabilities (12 low, 4 moderate)

To address issues that do not require attention, run:

npm audit fix

Some issues need review, and may require choosing

a different dependency.

Run npm audit for details.

npm notice npm-shrinkwrap.json up to date

make: *** [Makefile:89: electron-develop] Error 1

==> ERROR: A failure occurred in build().

Aborting...

error making: balena-etcher

================

HTH :)

EDIT: Stupid formatting...; not committing out-of-date flagging abuse.

Clemmitt Sigler

Spixmaster commented on 2021-03-15 13:38 (UTC)

@gin078 Could you please patch the PKGBUILD? It does not build anymore.

micwoj92 commented on 2021-03-09 11:38 (UTC)

Ask package maintainer not me.

Spixmaster commented on 2021-03-09 06:21 (UTC)

micwoj92 Why not just using the newest version of electron?

micwoj92 commented on 2021-03-08 18:02 (UTC)

@sl13kp use electron9-bin?

sl13kp commented on 2021-03-08 14:14 (UTC)

remove electron9 with newer version , because the mentioned package has lot of problems. thank you.

dimon7388 commented on 2021-03-04 16:39 (UTC)

Получил вот такую ошибку: Run npm audit for details. npm notice npm-shrinkwrap.json up to date make: *** [Makefile:89: electron-develop] Ошибка 1

Как решить эту проблему?

Spixmaster commented on 2021-03-03 18:44 (UTC)

I get the same error as SArpnt: make: *** [Makefile:89: electron-develop] Error 1

haibane commented on 2021-02-22 20:17 (UTC)

I've been getting this for months. ==> ERROR: Failure while downloading etcher git repo Aborting...

Any suggestions? I've tried clean builds and recently uninstall/reinstall.

SArpnt commented on 2021-02-16 00:18 (UTC)

@gin078 i found out it's just an issue on my setup, i still don't know what though. i was able to build fine on my laptop.

gin078 commented on 2021-02-15 13:22 (UTC)

@SArpnt are you still having issues building? I was unable to reproduce in a clean build environment.

SArpnt commented on 2021-02-06 23:18 (UTC)

when i try to build 1.5.116 i get:

make: *** [Makefile:89: electron-develop] Error 1

1.5.115 worked fine for me, is there anything i'm doing wrong?

BenTheTechGuy commented on 2020-12-01 02:57 (UTC)

Could you add i686, armv7h, and aarch64 to the arch section? The package can also be built on these architectures.

elhoce commented on 2020-11-04 19:17 (UTC)

After skipping sha256sum checks, package is working. So the issue comes from sha256sum signature provided in PKGBUILD

lpc123 commented on 2020-11-04 19:04 (UTC)

Confirmed failure reported by PongTea. Suspected issue: new electron9 dependency. Even after installing electron9, balena-etcher-electron.sh still fails.

PongTea commented on 2020-11-04 18:57 (UTC)

Building fails with this message:

==> Validating source files with sha256sums...
    etcher ... Skipped
    balena-etcher-electron.sh ... FAILED
    balena-etcher-electron.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build balena-etcher

gin078 commented on 2020-09-18 12:24 (UTC)

Thanks for reporting @allexj, I added patch as a proper dependency.

allexj commented on 2020-09-18 08:21 (UTC) (edited on 2020-09-18 08:24 (UTC) by allexj)

It failed for me, it says: Dependency missing: patch

So I had to do: sudo pacman -S patch

then it worked.

Also, I received this message: found 10 vulnerabilities (4 low, 6 high)run npm audit fix to fix them, or npm audit for details

Should I be worried?

yurikoles commented on 2020-06-17 20:46 (UTC)

Hi @gin078,

Please apply Arch Wiki advice on git submodules, e.g. like I did in etcher-git recently.

apastuszak commented on 2020-06-11 23:58 (UTC) (edited on 2020-06-11 23:59 (UTC) by apastuszak)

@gin078 nodejs-lts-carbon

gin078 commented on 2020-06-11 15:57 (UTC)

@apastuszak what node version are you using? I've just forced a rebuild in a pristine environment, and the build succeeded: https://travis-ci.org/github/xginn8/aur-bldr/jobs/694853704

apastuszak commented on 2020-06-11 13:57 (UTC) (edited on 2020-06-11 13:59 (UTC) by apastuszak)

This is giving me install problems:

35142 error code ELIFECYCLE
35143 error errno 1
35144 error electron-chromedriver@9.0.0 install: `node ./download-chromedriver.js`
35144 error Exit status 1
35145 error Failed at the electron-chromedriver@9.0.0 install script.
35145 error This is probably not a problem with npm. There is likely additional logging output above.
35146 verbose exit [ 1, true ]```

gin078 commented on 2020-06-01 13:53 (UTC)

@dalto fixed, thanks for reporting!

dalto commented on 2020-06-01 13:24 (UTC)

It looks like balena-etcher-electron.sh was updated without updating the sha256sum during the most recent update.

gin078 commented on 2020-05-28 13:06 (UTC)

@yurikoles thanks for the note, I've updated the package to use that same package.

yurikoles commented on 2020-05-28 10:55 (UTC)

Hi @gin078, I had created package electron9-bin, which is based on electron8-bin. I had tested it with my companion package, etcher-git, works good.

gin078 commented on 2020-05-25 18:12 (UTC)

v1.5.93 moves from electron7 to electron9, which is currently not available from community (being staged at the moment). Once that package is merged upstream, I will update balena-etcher.

gin078 commented on 2020-05-25 11:35 (UTC)

@bkb I was able to rebuild from source successfully in a pristine environment, can you try recloning from scratch?

bkb commented on 2020-05-24 16:29 (UTC)

[OK] Wrote shrinkwrap file to ../npm-shrinkwrap.json
added 1628 packages from 2393 contributors and audited 1636 packages in 101.751s

48 packages are looking for funding
  run `npm fund` for details

found 6 vulnerabilities (5 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
Dependency missing: patch
make: *** [Makefile:97: electron-develop] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
Error making: balena-etcher

gin078 commented on 2020-05-22 21:26 (UTC)

@apastuszak most drives should be detected automatically and Etcher will escalate privileges when required. The only exception to that is if you are flashing something like a compute module. In that case, you can use sudo to run the process as the root user if your user is allowed to sudo.

apastuszak commented on 2020-05-22 20:13 (UTC)

How do you run this as root?

dec commented on 2020-05-22 09:05 (UTC)

@gin078, thanks for quick reply everything is working fine :-) Cheers dec

gin078 commented on 2020-05-21 13:54 (UTC) (edited on 2020-05-21 13:55 (UTC) by gin078)

@dec that should be fixed now. Please let me know if you are still having issues, and thanks for reporting!

gin078 commented on 2020-05-21 12:38 (UTC)

@dec that is a regression upstream. I am talking to the maintainers to get it fixed. It seems like a dependent repository was made private.

dec commented on 2020-05-21 12:17 (UTC)

Hi @gin078, Package upgrade balena-etcher 2:1.5.90-1 is asking for username on github. A very strange behavior.

Cheers dec

gin078 commented on 2020-05-11 12:58 (UTC) (edited on 2020-05-11 12:59 (UTC) by gin078)

Hi @ekianjo,

re2 is a dependency of electron7, not Etcher directly.

ekianjo commented on 2020-05-09 05:00 (UTC)

This package is missing the dependency re2, it won't launch if not present, please fix! Thanks

gin078 commented on 2020-03-25 11:47 (UTC)

@huyizheng thanks for the note, I hadn't seen that package go into [community]. I've updated the package

huyz commented on 2020-03-25 03:06 (UTC)

Now electron7 is in community repo: https://www.archlinux.org/packages/community/x86_64/electron7/ So perhaps the dependency can be changed into electron7 rather than hard-coded electron7-bin.

Serial commented on 2020-03-09 21:03 (UTC)

Hello @gin078

I ended up installing this version of etcher: https://aur.archlinux.org/packages/etcher-bin

gin078 commented on 2020-03-09 13:57 (UTC)

@Serial that looks like a local networking issue or perhaps upstream issue with NPM, are you able to retry that build? I've just rebuilt it successfully from source.

Serial commented on 2020-03-09 01:14 (UTC)

npm ERR! A complete log of this run can be found in: npm ERR! /home/edson/.npm/_logs/2020-03-09T01_00_17_364Z-debug.log make: *** [Makefile:97: electron-develop] Erro 1 ==> ERROR: A build () failure occurred.      Aborting ...

16216 verbose type body-timeout 16217 verbose stack FetchError: Response timeout while trying to fetch http://registry.npmjs.org/lru-cache (over 30000ms) 16217 verbose stack at Timeout._onTimeout (/home/edson/.npm/_npx/31234/lib/node_modules/npm/node_modules/node-fetch-npm/src/body.js:189:16) 16217 verbose stack at listOnTimeout (internal/timers.js:549:17) 16217 verbose stack at processTimers (internal/timers.js:492:7) 16218 verbose cwd /var/tmp/pamac-build-edson/balena-etcher/src/etcher 16219 verbose Linux 5.5.8-arch1-1 16220 verbose argv "/usr/bin/node" "/home/edson/.npm/_npx/31234/bin/npm" "install" "--build-from-source" 16221 verbose node v13.10.1 16222 verbose npm v6.14.2 16223 error Response timeout while trying to fetch http://registry.npmjs.org/lru-cache (over 30000ms) 16224 verbose exit [ 1, true ]

wackbyte commented on 2020-02-22 21:53 (UTC) (edited on 2020-02-22 21:53 (UTC) by wackbyte)

I'm having the same problem as @LinuxIsBest, @romax, and @Serial, with the same logs as @romax. I tried rebuilding the package. (Arch Linux)

commented on 2020-02-19 23:51 (UTC)

I can confirm the bug @Serial reported on 2020-02-18 22:07

Unlike him/her I am using Arch Linux

Linux version 5.5.4-arch1-1 (linux@archlinux) (gcc version 9.2.1 20200130 (Arch Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Sat, 15 Feb 2020 00:36:29 +0000

romax commented on 2020-02-19 23:46 (UTC) (edited on 2020-02-19 23:49 (UTC) by romax)

Visible in the log (ctrl+shift+i then 'console' tab) is an npm related error:

Uncaught Error: The module '/usr/lib/balena-etcher/node_modules/xxhash/build/Release/hash.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 75. This version of Node.js requires
NODE_MODULE_VERSION 76. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:140)
    at process.func [as dlopen] (electron/js2c/asar.js:140)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1016)
    at Object.func (electron/js2c/asar.js:140)
    at Object.func [as .node] (electron/js2c/asar.js:140)
    at Module.load (internal/modules/cjs/loader.js:816)
    at Module._load (internal/modules/cjs/loader.js:728)
    at Module._load (electron/js2c/asar.js:717)
    at Function.Module._load (electron/js2c/asar.js:717)
    at Module.require (internal/modules/cjs/loader.js:853)
    at require (internal/modules/cjs/helpers.js:74)
    at Object.<anonymous> (/usr/lib/balena-etch…ash/lib/xxhash.js:4)
    at Object.<anonymous> (/usr/lib/balena-etch…sh/lib/xxhash.js:52)
    at Module._compile (internal/modules/cjs/loader.js:968)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:986)
    at Module.load (internal/modules/cjs/loader.js:816)

Serial commented on 2020-02-19 03:07 (UTC)

Once again the released package is in trouble, as can be seen in the image of the link below.

[img]https://i.imgur.com/Xkton17.gif[/img]

OS: ArcoLinuxB-deepin v20.2.12 Kernel: 5.5.4-arch1-1

gin078 commented on 2020-01-30 19:36 (UTC) (edited on 2020-01-30 19:41 (UTC) by gin078)

@Serial Manjaro has their own fully supported Etcher package, available here: https://gitlab.manjaro.org/packages/community/etcher. I recommend using that package, as this package is only intended for/supporting Arch Linux.

Serial commented on 2020-01-30 18:09 (UTC)

Hello people

I tried to install the new version of balena ecther on manjaro-Deepin 18.1.5 and it doesn't install, with the following error messages:

npm ERR! A complete log of this run can be found in: npm ERR! /home/edson/.npm/_logs/2020-01-30T17_52_13_056Z-debug.log make: *** [Makefile: 97: electron-develop] Error 1 ==> ERROR: A failure occurred in build ().      Aborting ...

gin078 commented on 2020-01-30 16:15 (UTC)

@Serial what WM/DE is that? I will try to reproduce locally and fix.

Serial commented on 2020-01-28 01:32 (UTC)

@gin078

I hadn't seen that there was another update to the balena-etcher version 2: 1.5.72-2

After updating this new version the problem was solved.

The only detail I noticed is that the icon on the taskbar is electron and not Balena-etcher, as seen in the image below:

https://imgur.com/GD7aRC2

Serial commented on 2020-01-28 01:05 (UTC)

The print is from version 2: 1.5.72-1 that has a problem, where it updated this afternoon.

At least it is the most recent version that appears here in the AUR

[img]https://i.imgur.com/sUMllRw.png[/img]

Follows the requested:

cat /usr/bin/balena-etcher-electron

!/bin/bash

ARGS="--no-sandbox" if [[ $EUID -ne 0 ]] || [[ $ELECTRON_RUN_AS_NODE ]]; then ARGS="" fi exec electron6 "${ARGS}" /usr/lib/balena-etcher "$@"

gin078 commented on 2020-01-28 00:50 (UTC)

@Serial is this gif having updated already to 2:1.5.72-2?

If so, can you provide the output of cat /usr/bin/balena-etcher-electron please?

Serial commented on 2020-01-28 00:39 (UTC)

@gin078

https://imgur.com/a/9ia3oHm

Thanks

gin078 commented on 2020-01-27 23:12 (UTC) (edited on 2020-01-27 23:12 (UTC) by gin078)

Sorry about that @Serial, should be fixed now (was my fault, a packaging problem).

Serial commented on 2020-01-27 22:52 (UTC)

They updated the balena etcher and when we click on the icon the electron V6.1.7 version opens and nothing of the balena-etcher app opens.

Each update of this program is a crap done.

ArcolinuzB-deepin 20.1.4

gin078 commented on 2020-01-12 19:46 (UTC)

@DragonX256 can you clarify what you mean? I am not seeing this behavior.

DragonX256 commented on 2020-01-10 09:46 (UTC)

Due to latest changes to PKGBUILD, it become devel-version. yay always offers to update package.

gin078 commented on 2020-01-08 16:15 (UTC)

@donbex the latest version should work around the submodule issue.

@gbr that dependency came from upstream here (https://github.com/balena-io/etcher/blob/5cfb95e8ea6db12df60aea19b47c8884e06b56c7/docs/USER-DOCUMENTATION.md#electron-specific) but I have confirmed the list of required dependencies and updated the package.

donbex commented on 2020-01-07 11:23 (UTC)

Trying to compile version 2:1.5.70-3, the build fails with the following error:

==> Starting prepare()...
From /tmp/makepkg/balena-etcher/src/scripts
 * [new branch]      makepkg    -> origin/makepkg
error: Server does not allow request for unadvertised object 39270eb2e5d72652f42f91ccd4cee1a66d41e06e
Fetched in submodule path 'scripts/resin', but it did not contain 39270eb2e5d72652f42f91ccd4cee1a66d41e06e. Direct fetching of that commit failed.
==> ERROR: A failure occurred in prepare().

gbr commented on 2020-01-03 19:50 (UTC)

Hey, can you please check if gconf is still necessary as a dependency? Thanks.

Serial commented on 2019-12-27 21:21 (UTC)

pksyua :: Synchronizing the package database ...  core is up to date  extra is up to date  community is up to date  multilib is up to date  arcolinux_repo is up to date  arcolinux_repo_3party is up to date  arcolinux_repo_submicron is up to date :: Starting full system update ... nothing to do :: Searching databases for updates ... :: Searching AUR for updates ...  -> Missing AUR Packages: deepin-manual qcef  -> Flagged Out Of Date AUR Packages: screenkey :: 1 Packages to upgrade. 1 aur / balena-etcher 2: 1.5.60-2 -> 2: 1.5.70-2 ==> Packages to exclude: (eg: "1 2 3", "1-3", "^ 4" or repo name) ==> :: Checking for conflicts ... :: Checking for inner conflicts ... [Aur: 1] balena-etcher-2: 1.5.70-2

1 balena-etcher (Installed) (Build Files Exist) ==> Packages to cleanBuild? ==> [N] one [A] ll [Ab] ort [I] nstalled [No] tInstalled or (1 2 3, 1-3, ^ 4) ==> :: PKGBUILD up to date, Skipping (1/1): balena-etcher   1 balena-etcher (Installed) (Build Files Exist) ==> Diffs to show? ==> [N] one [A] ll [Ab] ort [I] nstalled [No] tInstalled or (1 2 3, 1-3, ^ 4) ==> :: Parsing SRCINFO (1/1): balena-etcher ==> Creating the package: balena-etcher 2: 1.5.70-2 (Fri 27 Dec 2019 18:18:27 -03) ==> Getting fonts ...   -> Found v1.5.70.tar.gz   -> Updating repository scripts like git ... Fetching origin   -> Found balena-etcher-electron   -> Found balena-etcher-electron.desktop ==> Validating source files with sha256sums ...     v1.5.70.tar.gz ... Passed     scripts ... Ignored     balena-etcher-electron ... passed     balena-etcher-electron.desktop ... passed ==> Creating the package: balena-etcher 2: 1.5.70-2 (Fri 27 Dec 2019 18:18:32 -03) ==> Checking runtime dependencies ... ==> Checking build time dependencies ... ==> Getting fonts ...   -> Found v1.5.70.tar.gz   -> Updating repository scripts like git ... Fetching origin   -> Found balena-etcher-electron   -> Found balena-etcher-electron.desktop ==> Validating source files with sha256sums ...     v1.5.70.tar.gz ... Passed     scripts ... Ignored     balena-etcher-electron ... passed     balena-etcher-electron.desktop ... passed ==> Removing existing $ srcdir / directory ... ==> Extracting sources ...   -> Extracting v1.5.70.tar.gz with bsdtar   -> Creating working copy of repository scripts like git ... Cloning into 'scripts' ... done. ==> Starting prepare () ... /home/edson/.cache/yay/balena-etcher/PKGBUILD: line 35: cd: etcher: Nonexistent file or directory ==> ERROR: A failure has occurred in prepare ().     Aborting ... Error making: balena-etche

gin078 commented on 2019-12-20 18:13 (UTC) (edited on 2019-12-27 21:02 (UTC) by gin078)

@Serial 1.5.70 has been pushed to the AUR.

Serial commented on 2019-12-20 17:36 (UTC)

When will v1.5.70 be available via the AUR repository?

https://github.com/balena-io/etcher/releases

FrederickZh commented on 2019-11-07 02:03 (UTC)

https://aur.archlinux.org/packages/automake-1.15/ is needed to build the bundled lzma.

hugegameartgd commented on 2019-10-24 16:16 (UTC)

I get:

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/user/.npm/_npx/137412/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.3.7-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/home/user/.npm/_npx/137412/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64/lzma_native.node" "--module_name=lzma_native" "--module_path=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=electron-v3.1"
gyp ERR! cwd /run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /home/user/.npm/_npx/137412/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=electron-v3.1' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Linux 5.3.7-arch1-1-ARCH
node-pre-gyp ERR! command "/usr/bin/node" "/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native
node-pre-gyp ERR! node -v v12.13.0
node-pre-gyp ERR! node-pre-gyp -v v0.11.0
node-pre-gyp ERR! not ok 
Failed to execute '/usr/bin/node /home/user/.npm/_npx/137412/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/run/media/user/Windows/.cache/yay/balena-etcher/src/etcher/node_modules/lzma-native/binding-v4.0.5-electron-v3.1-linux-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=electron-v3.1' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lzma-native@4.0.5 install: `node-pre-gyp install --fallback-to-build && rimraf build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the lzma-native@4.0.5 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/user/.npm/_logs/2019-10-24T16_13_28_906Z-debug.log

I already tried installing those packages manually with npm, even globally.

gin078 commented on 2019-10-16 10:29 (UTC) (edited on 2019-10-18 13:04 (UTC) by gin078)

~~Building this package is currently broken due to an incompatibility with glibc 2.30, pending this PR: https://github.com/balena-io/node-ext2fs/pull/68. I am working on a workaround for the time being.~~

This issue should be fixed as of 1.5.60.

Spacecraft commented on 2019-10-13 01:20 (UTC)

Will not build: https://pastebin.com/Xg4aryxa

masterplayer31 commented on 2019-10-09 04:32 (UTC)

Will not build!

make[1]: *** [bindings.target.mk:110: Release/obj.target/bindings/src/node_ext2fs.o] Error 1 make[1]: Leaving directory '/home/bobby/.cache/yay/balena-etcher/src/etcher/node_modules/ext2fs/build' gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/home/bobby/.npm/_npx/21558/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:196:23) gyp ERR! stack at ChildProcess.emit (events.js:210:5) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12) gyp ERR! System Linux 5.3.5-arch1-1-ARCH gyp ERR! command "/usr/bin/node" "/home/bobby/.npm/_npx/21558/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/bobby/.cache/yay/balena-etcher/src/etcher/node_modules/ext2fs gyp ERR! node -v v12.11.1 gyp ERR! node-gyp -v v5.0.3 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! ext2fs@1.0.29 install: prebuild-install || node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ext2fs@1.0.29 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/bobby/.npm/_logs/2019-10-09T04_30_55_589Z-debug.log make: *** [Makefile:97: electron-develop] Error 1

gin078 commented on 2019-08-07 13:08 (UTC)

The package upgrading should be fixed now, sorry about the trouble!

PanisSupraOmnia commented on 2019-08-06 20:46 (UTC)

Oh, I see the issue. @gin078, you removed the epoch when you updated the version; the thing is, going forward, it has to stay as part of the version. So if you could re-add epoch=1 that should fix the issue with upgrading.

Serial commented on 2019-08-06 20:17 (UTC)

Electron3-bin is installed, but balena-etcher's new version 1.5.34-4) does not work.

balena-etcher: local (1: 1.5.34-4) is newer than AUR (1.5.53-1)

When looking for updates it removes the latest version in AUR and installs the version from the repository.

johncrist1988 commented on 2019-08-06 16:41 (UTC)

It appears that this package depends on electron3-bin available on the AUR.

Darkhogg commented on 2019-07-29 16:52 (UTC) (edited on 2019-07-29 16:54 (UTC) by Darkhogg)

the blank interface problem is happening to me in the current (1:1.5.34-4) version, making this unusable. If I start it on the terminal, I get this error:

Error: Error: ENOENT: no such file or directory, open '/usr/lib/balena-etcher/lib/dev-app-update.yml'

Serial commented on 2019-07-25 21:56 (UTC)

Após atualização do balena-etcher 1:1.5.34-4 o mesmo não funciona.

[2019-07-25 17:51] [ALPM] upgraded balena-etcher (1.5.50-1 -> 1:1.5.34-4)


After updating balena-etcher 1: 1.5.34-4 it does not work.

[2019-07-25 17:51] [ALPM] upgraded balena-etcher (1.5.50-1 -> 1: 1.5.34-4)

Kr1ss commented on 2019-07-24 18:08 (UTC) (edited on 2019-07-25 17:06 (UTC) by Kr1ss)

Otherwise it would be nice if @gin078 considered adding an epoch number

epoch=1

to the PKGBUILD, so that users of this package would get the downgrade automatically.

EDIT Thx for fixing so quickly !

PanisSupraOmnia commented on 2019-07-24 17:08 (UTC) (edited on 2019-07-24 17:09 (UTC) by PanisSupraOmnia)

@yuu if you installed the later versions of the package (anything beyond 1.5.34) it has a bug. For now, you'll need to force reinstallation of this package because it had to downgrade to 1.5.34. Specifically, it has to do with the version of electron that Balena uses to build etcher.

yuu commented on 2019-07-24 16:43 (UTC)

why blank the interface? I'm still googling looking for the answer. arch+plasma

PanisSupraOmnia commented on 2019-07-13 19:08 (UTC)

Hi, since this uses electron 4 it needs to depend on the "electron4" package, otherwise it fails to build.

Powersource commented on 2019-07-13 16:02 (UTC)

Getting an error when trying to install

==> Installing missing dependencies... error: target not found: electron<=4.1.4 ==> ERROR: 'pacman' failed to install missing dependencies. :: Unable to build balena-etcher - makepkg exited with code: 8

digaoddc commented on 2019-05-15 13:53 (UTC)

@gin078 Thank you very much, it is working with the downgrade.

gin078 commented on 2019-05-14 10:31 (UTC)

@digaoddc I am working on a patch to fix that, I have downgraded the package to the latest stable version in the meantime (v1.5.34).

digaoddc commented on 2019-05-14 09:05 (UTC)

I installed etcher yesterday, and it only displays the buttons. The rest of the interface is empty. I am unable to do anything.

gin078 commented on 2019-05-13 12:00 (UTC)

This package will be merged with https://aur.archlinux.org/packages/balena-etcher/ after upstream's rename: https://www.balena.io/blog/resin-io-changes-name-to-balena-releases-open-source-edition/.

gin078 commented on 2019-05-08 03:54 (UTC)

@bigolewannabe the most recent release is 1.5.33 (https://github.com/balena-io/etcher/tags), what version do you have installed?

timhs commented on 2019-05-06 10:07 (UTC)

@gin078 thank you very much I got it to update it now. Had to deinstall npm with pacman then delete /usr/lib/node-modules/npm then install npm with pacman again. Problem is the mixture of local and global of npm.

gin078 commented on 2019-05-06 05:22 (UTC) (edited on 2019-05-06 08:31 (UTC) by gin078)

@timhs I think you may need to clean up all the build artifacts and try again. Can you try building with makepkg -C to clean up $srcdir before building?

timhs commented on 2019-05-05 18:27 (UTC) (edited on 2019-05-05 18:28 (UTC) by timhs)

I get this error while updating Cannot find module 'readable-stream/transform' If I try #npm update -g I get the same error?

haavard commented on 2019-04-14 20:28 (UTC)

I'm going to disown this package. Upstream is too tied to specific Electron versions, and building against system Electron requires a lot of work. On top of this, they keep changing up their build system, so every update requires a new workaround. With the Electron/Node ecosystem being what it is, building this from source just isn't a good fit. Try etcher-bin.

stefnix commented on 2019-04-14 20:04 (UTC) (edited on 2019-04-14 20:05 (UTC) by stefnix)

Now it doesn't even work properly. https://i.imgur.com/3FsLzfd.png

I know I could apply the fixes to the PKGBUILD myself, but I think it's best for the maintainer to step it up.

haavard commented on 2019-04-12 06:31 (UTC)

dylanmtaylor: it doesn't.

dylanmtaylor commented on 2019-04-12 03:17 (UTC)

Upstream seems to be on electron 4, not sure why this requires electron 2

haavard commented on 2019-04-09 14:20 (UTC)

The submodule issue should be resolved in 1.5.24 - blame upstream. I'll update the package this Saturday, or Sunday at the latest.

a.kudelin commented on 2019-04-09 13:51 (UTC)

+1 Crush during submodule updating

DmAsB commented on 2019-04-09 13:49 (UTC)

Same issue as @jose1711

hriad commented on 2019-04-06 23:19 (UTC)

Same issue as @jose1711

jose1711 commented on 2019-04-05 14:31 (UTC)

Submodule 'scripts/resin' (https://github.com/balena-io/scripts.git) registered for path 'scripts/resin'
Cloning into '../src/etcher/scripts/resin'...
done.
error: Server does not allow request for unadvertised object 481cacb7f1533985507c84f28940cada0fb109e5
Fetched in submodule path 'scripts/resin', but it did not contain 481cacb7f1533985507c84f28940cada0fb109e5. Direct fetching of that commit failed.

haavard commented on 2019-03-27 20:46 (UTC)

Thanks for the (now valid) out-of-date flag. I won't get to updating the package until this weekend, unfortunately.

ajgraves commented on 2019-03-27 20:45 (UTC)

1.5.18 is available on https://www.balena.io/etcher/

haavard commented on 2019-03-13 20:36 (UTC)

Please don't flag the package as out of date: the latest version available on https://www.balena.io/etcher/ is 1.5.5.

haavard commented on 2019-03-09 10:19 (UTC)

The package script installs usr/share/applications/etcher-electron.desktop. This sounds like an issue on your end. Check if the built package tarball contains usr/share/applications/etcher-electron.desktop.

dangelov commented on 2019-03-07 07:36 (UTC) (edited on 2019-03-07 07:36 (UTC) by dangelov)

I have the same issue as @abdulhakeem. The package installed but there's no way to launch it. Doing ls /usr/share/applications/etcher-electron.desktop returns No such file or directory.

haavard commented on 2019-03-04 22:45 (UTC)

You're right, that was omitted from the push due to some commit-hook shenanigans. Fixed now -- sorry about the trouble :)

Kr1ss commented on 2019-03-04 22:40 (UTC) (edited on 2019-03-04 22:45 (UTC) by Kr1ss)

@haavard Seems u forgot to update the sha256 hash for etcher-electron in the PKGBUILD file.

Cheers !

EDIT Wow that was a quick fix lol. :D Thx

Krychek commented on 2019-02-18 15:00 (UTC)

Replying to myself... I'm using antergos and they have their own version that shadows this one. Running yaourt etcher let me choose this package instead of the default one.

Krychek commented on 2019-02-18 14:58 (UTC)

I have just installed this package, but the version I got is 1.4.4 instead of 1.4.9. Could you someone else verify this?

haavard commented on 2019-01-27 16:38 (UTC)

medicineman25: this doesn't seem like a packaging issue, and I can't reproduce it. Seems likely something about your network setup is off.

medicineman25 commented on 2019-01-27 08:21 (UTC) (edited on 2019-01-27 08:22 (UTC) by medicineman25)

Getting this error:

npm WARN tarball tarball data for simple-progress-webpack-plugin@https://registry.npmjs.org/simple-progress-webpack-plugin/-/simple-progress-webpack-plugin-1.1.2.tgz (sha512-bNQfb3qSqbtsfxg6d0dGechUUJH2lZqKG5+bj2aoJmEA0rSzcm+2JVfC2YgkDABfuGItZ/O5ttt6BssWZW4SNg==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for angular@https://registry.npmjs.org/angular/-/angular-1.6.3.tgz (sha512-GEr8LYsE0pXmryfZj7wlmV3+yAqoPt6slcuklJG7vLqNBBAH6A/N2Kc1O5SR2dnaUwIWOJHRlh2Ajlnimlf//A==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for @fortawesome/fontawesome-free-webfonts@https://registry.npmjs.org/@fortawesome/fontawesome-free-webfonts/-/fontawesome-free-webfonts-1.0.9.tgz (sha512-nLgl6b6a+tXaoJJnSRw0hjN8cWM/Q5DhxKAwI9Xr0AiC43lQ2F98vQ1KLA6kw5OoYeAyisGGqmlwtBj0WqOI5Q==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for ajv@https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz (sha512-Ajr4IcMXq/2QmMkEmSvxqfLN5zGmJ92gHXAeOXq1OekoH2rfDNsgdDoL2f7QaRCy7G/E6TpxBVdRuNraMztGHw==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for rabin-bindings@https://registry.npmjs.org/rabin-bindings/-/rabin-bindings-1.7.4.tgz (sha512-4Ml+Hsw1asNttafMFF+GWgGOcZs9nJk7qb3GE9eyihMUOrxFVcKeKcfeCncTSIPYsfWNvdf4yc0GGbHPUiQYjg==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for showdown@https://registry.npmjs.org/showdown/-/showdown-1.9.0.tgz (sha512-x7xDCRIaOlicbC57nMhGfKamu+ghwsdVkHMttyn+DelwzuHOx4OHCVL/UW/2QOLH7BxfCcCCVVUix3boKXJKXQ==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for eslint@https://registry.npmjs.org/eslint/-/eslint-2.13.1.tgz (sha512-29PFGeV6lLQrPaPHeCkjfgLRQPFflDiicoNZOw+c/JkaQ0Am55yUICdYZbmCiM+DSef+q7oCercimHvjNI0GAw==) seems to be corrupted. Trying one more time. npm WARN tarball tarball data for 7zip-bin-linux@~1.3.1 (sha512-Wv1uEEeHbTiS1+ycpwUxYNuIcyohU6Y6vEqY3NquBkeqy0YhVdsNUGsj0XKSRciHR6LoJSEUuqYUexmws3zH7Q==) seems to be corrupted. Trying one more time.

haavard commented on 2019-01-23 19:17 (UTC)

Yes, it requires electron2. This is in the official repos, so that should not be a problem.

For the app menu, this package installs virtually the same .desktop file as the upstream package. Can you verify that /usr/share/applications/etcher-electron.desktop exists and is owned by this package?

abdulhakeem commented on 2019-01-23 03:47 (UTC)

This doesn't seem to work... it requires electron2, so I have both electron2 and electron3 installed on my system, and then once you install etcher, it doesn't actually appear anywhere. In GNOME, it's completely absent from the app menu, so there's no way to actually launch and use it. Uninstalling, seeing if maybe the etcher-bin package is any different. This worked fine for years up until like 2-3 months ago, idk what happened.

astro commented on 2018-12-05 07:59 (UTC)

Hi, I have a npm error with the last update : Trying to find linux-electron-2.0.12-x64-3b7f564fa3af27bd500b351171c102d3b5117f3858c530d30196b9959c2dac0a.tar.gz... Rebuilding native modules Installing dependencies 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! npm ERR! code E418 npm ERR! 418 I'm a teapot: @fortawesome/fontawesome-free-webfonts@https://registry.npmjs.org/@fortawesome/fontawesome-free-webfonts/-/fontawesome-free-webfonts-1.0.9.tgz

I'm a Teapot !?? 418 ?? The URL "https://registry.npmjs.org/@fortawesome/fontawesome-free-webfonts/-/fontawesome-free-webfonts-1.0.9.tgz" is correct.

imrehg commented on 2018-11-19 09:56 (UTC)

@haavard see my comment below, for the AWS_ACCESS_KEY needs make electron-develop -i, and that is not make -i, but the flag to "do not upload cache" https://github.com/balena-io/scripts/blob/8baa9e9a4063edc0b597baf16e266e28ed460b94/shared/npm-install.sh#L44

haavard commented on 2018-11-18 17:37 (UTC)

For the error AWS_ACCESS_KEY_ID, this is due to a bug in the Etcher build system (issue submitted here). Temporary workarounds are to make the aws command unavailable (e.g. uninstall aws-cli or build in a chroot).

Additionally, 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! is not an error, just a warning, and can be ignored.

haavard commented on 2018-11-18 17:36 (UTC)

imrehg: make -i simply tells make to ignore errors, which may coincidentally make Etcher build in this case, but can't be enabled in general at a package level.

imrehg commented on 2018-11-13 15:27 (UTC) (edited on 2018-11-13 15:28 (UTC) by imrehg)

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/npm-install.sh: 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 (UTC)

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: github.com/balena-io/scripts.git 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 (UTC)

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 (UTC) (edited on 2018-11-08 21:52 (UTC) by ector)

yes. I have no dns use netctl default

luisnabais commented on 2018-11-06 17:19 (UTC)

Thanks a lot haavard, that was it. Cheers

haavard commented on 2018-11-06 10:39 (UTC)

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 (UTC) (edited on 2018-11-06 10:01 (UTC) by luisnabais)

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

haavard commented on 2018-11-04 12:12 (UTC)

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

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

ector commented on 2018-11-03 17:07 (UTC) (edited on 2018-11-03 17:08 (UTC) by ector)

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?

haavard commented on 2018-11-03 14:21 (UTC)

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

ector commented on 2018-11-03 13:53 (UTC)

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

ector commented on 2018-11-03 13:50 (UTC)

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

haavard commented on 2018-11-01 19:55 (UTC) (edited on 2018-11-01 19:56 (UTC) by haavard)

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.

Zeioth commented on 2018-11-01 19:06 (UTC)

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

haavard commented on 2018-11-01 06:39 (UTC)

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

prurigro commented on 2018-11-01 03:26 (UTC)

The build dependency jq is missing for the latest version

haavard commented on 2018-10-28 10:50 (UTC) (edited on 2018-10-28 10:51 (UTC) by haavard)

vosskaem, I suggest you take a look at some of the Stack Overflow questions linked below. This is unlikely to be a packaging issue, but an issue with your proxy/network situation.

https://stackoverflow.com/questions/4891527/git-protocol-blocked-by-company-how-can-i-get-around-that https://stackoverflow.com/questions/31113433/accessing-github-behind-corporate-proxy-node-js

vosskaem commented on 2018-10-27 14:17 (UTC)

Unable to build behind proxy: npm ERR! Error while executing: npm ERR! /usr/bin/git ls-remote -h -t git://github.com/jviotti/webpack.git npm ERR! npm ERR! fatal: unable to connect to :github.com:

SpectralMemories commented on 2018-09-15 01:02 (UTC)

FFY00 That would be awesome of you, for real

FFY00 commented on 2018-09-07 16:23 (UTC)

Hey, sorry for not following up. I have run into some issues when trying to make the package use the system's electron. I have been a bit busy and I totally forgot to contact you. I still plan to move the package but I need time to make it work properly. When it's ready (no clue on the ETA), I'll ping you here ;) Thank you.

FFY00 commented on 2018-08-24 18:58 (UTC)

Thank you. I'll release the package and delete it from AUR once most of the mirrors have synced with the main server :)

haavard commented on 2018-08-24 18:52 (UTC)

Hey FFY00, no objections to that :)

FFY00 commented on 2018-08-24 18:49 (UTC)

Hello, I want to move this package to [community]. Do you have any problems with that?

ector commented on 2018-05-01 20:04 (UTC)

today i have this erorrs ==> Aggiornamenti del software (nuova versione): aur/etcher 1.3.1-3 -> 1.4.4-1 aur/inxi 3.0.03-1 -> 3.0.07-1

==> Continuare l'aggiornamento? [S/n] ==> [V]edi i dettagli dei pacchetti Seleziona [M]anualmente i pacchetti ==> --------------------------------------------------------------------- ==> y

==> Scaricamento del PKGBUILD di etcher da AUR... x .SRCINFO x .gitignore x PKGBUILD x etcher-electron x etcher-electron.desktop haavard commented on 2018-04-29 14:27

tuxayo commented on 2018-04-29 18:03

tuxayo commented on 2018-04-29 18:29

nebiros commented on 2018-05-01 09:32

haavard commented on 2018-05-01 15:24

etcher 1.4.4-1 (2018-04-28 19:23) ( Pacchetto non supportato: Potenzialmente pericoloso! ) ==> Modificare PKGBUILD [S/n] ("A" per annullare) ==> ---------------------------------------------- ==> n

==> Dipendenze di etcher - electron (già installato) - gtk2 (già installato) - libxtst (già installato) - libxss (già installato) - gconf (già installato) - nss (già installato) - alsa-lib (già installato) - npm (già installato) [makedepend] - python2 (già installato) [makedepend] - git (già installato) [makedepend]

==> Continuare la compilazione di etcher [S/n] ==> ------------------------------------------ ==> s

==> Compilazione e installazione del pacchetto ==> Creazione del pacchetto: etcher 1.4.4-1 (mar 1 mag 2018, 21.59.04, CEST) ==> Controllo delle dipendenze durante l'avvio in corso... ==> Controllo delle dipendenze durante la compilazione in corso... ==> Download dei sorgenti in corso... -> Download di v1.4.4.tar.gz in corso... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 123 0 123 0 0 184 0 --:--:-- --:--:-- --:--:-- 184 100 40.0M 100 40.0M 0 0 1222k 0 0:00:33 0:00:33 --:--:-- 1321k -> È stato trovato etcher-electron -> È stato trovato etcher-electron.desktop ==> Validazione di source file con sha256sums... v1.4.4.tar.gz ... Verificato etcher-electron ... Verificato etcher-electron.desktop ... Verificato ==> Estrazione dei sorgenti in corso... -> Estrazione di v1.4.4.tar.gz usando bsdtar in corso... ==> Avvio di prepare() in corso... ==> Avvio di build() in corso... 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! npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end

npm ERR! A complete log of this run can be found in: npm ERR! /home/bob/.npm/_logs/2018-05-01T20_01_47_963Z-debug.log ==> ERRORE: Si è verificato un errore in build(). L'operazione sta per essere interrotta... ==> ERRORE: Makepkg non è riuscito a compilare etcher. ==> Riavviare la compilazione di etcher [s/N] ==> ----------------------------------------- ==>

haavard commented on 2018-05-01 15:24 (UTC) (edited on 2018-05-01 15:25 (UTC) by haavard)

If building fails with "ERR_STREAM_WRITE_AFTER_END", this is a bug in npm. Try downgrading to npm 5.6.0 as discussed here. Simply retrying the build or building in a chroot may also work.

nebiros commented on 2018-05-01 09:32 (UTC)

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! npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end

npm ERR! A complete log of this run can be found in: npm ERR! /home/nebiros/.npm/_logs/2018-05-01T09_31_22_840Z-debug.log ==> FEHLER: Ein Fehler geschah in build(). Breche ab...

tuxayo commented on 2018-04-29 18:29 (UTC)

Well I just retried and it compiled. It might have been fixed in an upstream npm package. @mozzi32 can you retry?

tuxayo commented on 2018-04-29 18:03 (UTC)

I have the same issue with an up to date system

haavard commented on 2018-04-29 14:27 (UTC)

mozzi32: is your system fully up to date? Google points to a possible bug in npm, do any of the steps outlined here solve the problem? https://github.com/npm/npm/issues/19989

mozzi32 commented on 2018-04-29 00:30 (UTC)

Hi

Upgrade with version 1.4.4.1 is wrong for me : "==> Lancement de build()... 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! npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end" I'm with Archlinux and Gnome. Thanks

GPereira commented on 2018-04-21 09:36 (UTC)

Hi, can I comantain this package with you?

ector commented on 2018-04-20 15:20 (UTC)

gyp info ok (node:21306) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit removed 853 packages in 21.86s ==> Entro nell'ambiente fakeroot... ==> Avvio di package() in corso... ==> Rimozione dei dati superflui in corso... -> Rimozione dei file libtool in corso... -> Eliminazione dei file indesiderati in corso... -> Rimozione dei file dalle librerie statiche... -> Rimozione dei simboli non necessari dai binari e dalle librerie in corso... strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-tuklib_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-tuklib_cpucores.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_util.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-easy_preset.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-hardware_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-index.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_flags_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-vli_size.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-alone_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_header_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-easy_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-easy_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-easy_encoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-index_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-vli_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-hardware_cputhreads.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-outqueue.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_encoder_mt.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-alone_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-auto_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-block_header_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-easy_decoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-filter_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-index_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-index_hash.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-stream_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-vli_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-check.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-crc32_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-crc32_fast.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-crc64_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-crc64_fast.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-sha256.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lz_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lz_encoder_mf.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lz_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma_encoder_presets.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma_encoder_optimum_fast.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma_encoder_optimum_normal.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-fastpos_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma2_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-lzma2_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-price_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-delta_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-delta_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-delta_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-simple_coder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-simple_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-simple_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-powerpc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-ia64.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-arm.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-armthumb.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_la-sparc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-x86-64.a(liblzma_w32res.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-tuklib_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-tuklib_cpucores.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_util.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-easy_preset.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-hardware_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-index.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_flags_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-vli_size.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-alone_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_header_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-easy_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-easy_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-easy_encoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-index_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-vli_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-hardware_cputhreads.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-outqueue.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_encoder_mt.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-alone_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-auto_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-block_header_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-easy_decoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-filter_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-index_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-index_hash.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-stream_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-vli_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-check.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-crc32_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-crc32_x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-crc64_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-crc64_x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-sha256.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lz_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lz_encoder_mf.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lz_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma_encoder_presets.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma_encoder_optimum_fast.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma_encoder_optimum_normal.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-fastpos_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma2_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-lzma2_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-price_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-delta_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-delta_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-delta_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-simple_coder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-simple_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-simple_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-powerpc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-ia64.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-arm.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-armthumb.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_la-sparc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/liblzma-i686.a(liblzma_w32res.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbt.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbh.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00097.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00096.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00095.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00094.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00093.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00092.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00091.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00090.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00089.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00088.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00087.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00086.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00085.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00084.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00083.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00082.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00081.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00080.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00079.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00078.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00077.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00076.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00075.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00074.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00073.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00072.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00071.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00070.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00069.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00068.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00067.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00066.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00065.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00064.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00063.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00062.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00061.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00060.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00059.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00058.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00057.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00056.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00055.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00054.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00053.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00052.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00051.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00050.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00049.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00048.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00047.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00046.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00045.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00044.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00043.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00042.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00041.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00040.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00039.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00038.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00037.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00036.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00035.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00034.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00033.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00032.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00031.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00030.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00029.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00028.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00027.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00026.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00025.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00024.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00023.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00022.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00021.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00020.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00019.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00018.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00017.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00016.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00015.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00014.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00013.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00012.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00011.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00010.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00009.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00008.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00007.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00006.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00005.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00004.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00003.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00002.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00001.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/doc/lzma.lib(dhgpbs00000.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-tuklib_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-tuklib_cpucores.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_util.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-easy_preset.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-hardware_physmem.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-index.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_flags_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-vli_size.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-alone_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_header_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-easy_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-easy_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-easy_encoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-index_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_buffer_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_flags_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-vli_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-hardware_cputhreads.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-outqueue.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_encoder_mt.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-alone_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-auto_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-block_header_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-easy_decoder_memusage.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-filter_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-index_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-index_hash.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_buffer_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-stream_flags_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-vli_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-check.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-crc32_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-crc32_x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-crc64_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-crc64_x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-sha256.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lz_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lz_encoder_mf.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lz_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma_encoder_presets.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma_encoder_optimum_fast.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma_encoder_optimum_normal.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-fastpos_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma2_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-lzma2_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-price_table.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-delta_common.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-delta_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-delta_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-simple_coder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-simple_encoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-simple_decoder.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-x86.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-powerpc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-ia64.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-arm.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-armthumb.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_la-sparc.o): Impossibile riconoscere il formato del file: File format not recognized strip:./usr/share/etcher/node_modules/lzma-native/deps/bin_i686/liblzma.a(liblzma_w32res.o): Impossibile riconoscere il formato del file: File format not recognized

strip: Impossibile riconoscere il formato del file di input "./usr/share/etcher/lib/blobs/usbboot/raspberrypi/start_cd.elf" -> Compressione delle pagine man ed info in corso... ==> Controllo per il rilascio dei pacchetti in corso... ==> 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...

haavard commented on 2018-04-16 15:28 (UTC)

Pushed 1.3.1-3 with a .desktop file (and icons).

DragonX256 commented on 2018-04-16 02:02 (UTC)

There is no .desktop file for Etcher after install.

RemoteAdmin commented on 2018-04-14 05:54 (UTC)

jq is missing as a makedepends

Makefile:188: No Sentry token found (ANALYTICS_SENTRY_TOKEN is not set)
Makefile:194: No Mixpanel token found (ANALYTICS_MIXPANEL_TOKEN is not set)
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
/bin/bash: jq: command not found
./scripts/build/dependencies-npm.sh \
    -r "x64" \
    -v "" \
    -t electron \
    -s "linux"
Dependency missing: python
make: *** [Makefile:531: electron-develop] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

ams1 commented on 2018-04-13 12:05 (UTC)

Yup, 1.4.1 has been pulled.

https://forums.resin.io/t/etcher-v1-4-1-unpublished/2912

ams1 commented on 2018-04-13 12:02 (UTC)

Etcher 1.4.1 is not out on etcher.io. 1.4.0 didn't happen either. Presumably they have problems.

ams1 commented on 2018-04-12 20:50 (UTC)

I couldn't figure out how to do "electron properly", so this package is now orphaned.

ams1 commented on 2018-04-12 20:47 (UTC)

I've now created etcher-bin. Unless somebody implements a source build here, future updates will go there.

eschwartz commented on 2018-04-12 14:39 (UTC)

Nothing is stopping you from using upstream's painful build system to generate the app itself, then creating your own wrapper script that calls the system electron via e.g. electron /usr/share/etcher-app/ (and of course installing just the resources directory... to usr/share/). This is how to do electron apps the right way, if upstream doesn't make it easy.

Nothing is stopping you from building this from source, with prebuilt electron webpack, then installing that to /opt like this package currently does.

OTOH this package as-is, is an open-source program with source code available, which uses repackaged .deb packages in a manner that completely violates AUR naming standards for -bin packages.

ams1 commented on 2018-04-12 14:30 (UTC)

I suppose moving it to etcher-bin makes sense. Likewise for etcher-cli.

coderobe commented on 2018-04-12 13:22 (UTC) (edited on 2018-04-12 13:23 (UTC) by coderobe)

If you don't feel like fixing your pkgbuild, create etcher-bin and merge this so that others:

  • can tell by the name it's a bin package

  • can upload a proper etcher package that builds from source

Alternatively, feel free to orphan the package.

ams1 commented on 2018-04-12 12:22 (UTC)

@coderobe The etcher makefile is designed to build the installers. It has a development mode, but there's no "proper install". The build process bundles a lot of npm modules, and electron itself. It might be possible to subvert it somehow, but the result would be fragile, and without doing that we get a bunch of files unsuitable for /usr.

I'm not sure there's much advantage in what you're asking for.

coderobe commented on 2018-04-11 14:02 (UTC)

Please update the PKGBUILD to build etcher from source, and properly install the binary instead of using /opt.

tuxayo commented on 2018-03-19 19:25 (UTC)

@wox If would be even better if the package was handling this, to not require manual post install operations. And to avoid creating a file not handled by the package manager.

wox commented on 2018-03-14 13:10 (UTC)

sudo ln -s /opt/Etcher/etcher-electron /usr/bin/etcher

Powersource commented on 2018-03-13 21:29 (UTC)

Could you please put the binary on the PATH?

assarawaki commented on 2018-03-13 00:48 (UTC)

==> ERROR: Aborted by user! Exiting... ==> ERROR: A failure occurred in build(). Aborting...

What happened ?

Ybalrid commented on 2018-03-06 18:08 (UTC)

Just so you know guys, the package installs the application into /opt/Etcher. It wasn't obvious for me at first, so I hope this comment will help somebody else like me. :)

samholmes commented on 2018-01-07 23:26 (UTC) (edited on 2018-01-07 23:26 (UTC) by samholmes)

Absolutely alright Andrew, thank you for making this package! :)

ams1 commented on 2018-01-07 21:00 (UTC)

Apparently I jumped the gun a little. Oh well, update reverted, for now.

I should look at the web site, not just github. :-(

dudenugget2000 commented on 2018-01-07 18:31 (UTC) (edited on 2018-01-07 18:32 (UTC) by dudenugget2000)

I'm getting the same curl error as everyone else:

curl: (22) The requested URL returned error: 404 Not Found

Kewl commented on 2018-01-07 18:09 (UTC)

@ams1 The package should be rolled back until 1.3.0 or 1.3.1 can build don't you think?

badbrain commented on 2018-01-07 14:04 (UTC)

curl: (22) The requested URL returned error: 404 Not Found

ndttt commented on 2018-01-07 07:36 (UTC)

Same error as the previous 3 comments.

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading https://github.com/resin-io/etcher/releases/download/v1.3.0/etcher-electron_1.3.0_amd64.deb Aborting... The build failed.

astro commented on 2018-01-06 23:51 (UTC)

https://github.com/resin-io/etcher/releases/download/v1.3.0/etcher-electron_1.3.0_amd64.deb

Yes, 404 | not found ...

saildata commented on 2018-01-06 18:27 (UTC)

I was confused too - so I looked around and I think I found the mismatch: - v1.3.0 was pushed in a commit yesterday (https://github.com/resin-io/etcher/commit/ece9a5666ee5fff52816e590d93fec3a24982402) - The builds on Travis CI have already switched to 1.3.0 - There is a release checklist that is not finished yet, so I think that's what they are waiting for to push the binary builds (https://github.com/resin-io/etcher/pull/1954) - Waiting for: - Publish packages on S3 - Mailing list update

NOTE: While looking at open bugs I saw (https://github.com/resin-io/etcher/issues/1955) which looks like an overflow that you want to wait for. There are a couple others open if you search for 1.3.0. I'll be waiting a little while to see the major stuff get ironed out. --Cheers

abdulhakeem commented on 2018-01-06 18:01 (UTC)

I'm getting the following error when trying to update (using pacaur if that matters, I know it's unmaintained but it seems to still be working):

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading https://github.com/resin-io/etcher/releases/download/v1.3.0/etcher-electron_1.3.0_amd64.deb Aborting... :: failed to verify etcher integrity

ams1 commented on 2017-12-24 18:06 (UTC)

@Plexcon, it's been updated to v1.2.1 since the 8th. What am I missing?

Plexcon commented on 2017-12-24 16:55 (UTC) (edited on 2017-12-24 16:55 (UTC) by Plexcon)

Update, please v.1.2.1.x

ams1 commented on 2017-11-30 13:51 (UTC)

@ph9214, I've built it with makepkg, in a clean chroot with extra-x86_64-build, and under pacaur. All work fine. Are you using a different AUR helper?

ph9214 commented on 2017-11-29 20:01 (UTC)

this now fails with /usr/bin/fakeroot: line 1: kill: (760) - No such process

ams1 commented on 2017-11-26 16:23 (UTC)

@pjpreilly, I don't know, but I removed it because I can't do a test build anymore. Maybe there's a new way to get a clean 32-bit chroot setup?

pjpreilly commented on 2017-11-24 22:12 (UTC)

How does i686 package get added to Archlinux32?

ams1 commented on 2017-11-24 13:35 (UTC)

@imrehg, please see the comments below. etcher-cli owns /usr/bin/etcher now.

imrehg commented on 2017-11-24 11:18 (UTC)

Hi, thanks for the new version! It seems like that after the update Etcher can just be run from the start menu. Would be great to have the symlink back to `/usr/bin/` so it can be run from the terminal as well (that is symlink /opt/Etcher/etcher-electron to /usr/bin/etcher as it was before) You think it would be possible?

ams1 commented on 2017-10-13 15:28 (UTC)

@oldgaro, that's not caused by the .deb change. That's because /bin/etcher now belongs to etcher-cli. You can type /opt/Etcher/etcher-electron if starting it from your DE isn't enough.

oldgaro commented on 2017-10-13 14:41 (UTC) (edited on 2017-10-13 15:12 (UTC) by oldgaro)

type -a etcher etcher not found! ... PS: appimage sounds a better idea than .deb crappy...

014 commented on 2017-10-07 17:03 (UTC)

I just have to say thanks for packaging this for Arch. Etcher is a great utility!

ams1 commented on 2017-08-22 22:21 (UTC)

There's a package for the CLI now. :-)

ams1 commented on 2017-08-10 08:43 (UTC)

There's a new experimental etcher CLI command that uses that name, so I deliberately let it change. (There's no AUR package for the CLI yet.)

imrehg commented on 2017-08-10 08:36 (UTC)

Would be nice to keep the `etcher` command as well, as got used to starting Etcher from the command line instead of the menu. Added the symlink in my own version of the package. mkdir -p "${pkgdir}/usr/bin/" ln -s "/opt/Etcher/etcher-electron" "${pkgdir}/usr/bin/etcher"

ams1 commented on 2017-08-08 11:43 (UTC)

The binaries come *from* the .deb files. Of course the pacman package is tar.xz The package takes more space because the electron stuff is no longer compressed inside a .AppImage file.

now-im commented on 2017-08-08 11:40 (UTC)

Why use .deb binaries? As far as I know .tar.xz or .zip is the standard for arch linux. Maybe this is the reason of this package taking more space. Packages (1) etcher-1.1.2-1 Total Installed Size: 175.07 MiB Net Upgrade Size: 113.29 MiB

ams1 commented on 2017-08-08 10:38 (UTC)

As of 1.1.2, this package uses the binaries from the .deb files.

daijizai commented on 2017-08-06 01:01 (UTC)

Needs depends on extra/libxss

ams1 commented on 2017-07-25 23:04 (UTC)

I seem to have been premature. The 32bit AppImage is available now and I've updated the PKGBUILD.

ams1 commented on 2017-07-25 17:01 (UTC)

v1.1.1 is up now, but there's no i686 AppImage any more (no idea if that's deliberate). I updated to use only x86_64, for now. I can switch to use the .deb binaries if anybody cares about i686, but that'll take a bit more time than I have now.

now-im commented on 2017-07-22 06:19 (UTC)

@ams1 I am sorry for flagging the package out of date without knowing the existing issue. There is no way to undo that.

ams1 commented on 2017-07-21 20:11 (UTC)

Probably caused by this bug: https://github.com/resin-io/etcher/issues/1617

ams1 commented on 2017-07-21 20:04 (UTC)

Huh? The website has rolled back to v1.0.0 as well. They must have withdrawn the release? I'll revert the update.

vlamnire0 commented on 2017-07-21 20:01 (UTC)

The latest update has an invalid url. ==> ERROR: Failure while downloading https://github.com/resin-io/etcher/releases/download/v1.1.0/etcher-1.1.0-linux-x64.zip

ams1 commented on 2017-06-29 09:48 (UTC)

The hash algorithm is not the weak link in the chain here, but it's a simple change to make, so next update I will.

gok commented on 2017-06-29 08:41 (UTC)

Thanks for the PKGBUILD. Given MD5 and SHA1 are not secure anymore, could you consider switching from MD5 checksums to SHA256 ones?

DJ9 commented on 2017-04-15 20:36 (UTC)

Btw, it should be Etcher-1.0.0-rc.3-linux-x64.zip

DJ9 commented on 2017-04-15 20:20 (UTC)

I'm getting a 404 error on finding the file to download from Amazon. "The requested URL returned error: 404 Not Found" ERROR: Failure while downloading https://resin-production-downloads.s3.amazonaws.com/Etcher-1.0.0-rc.2-linux-x64.zip

Cirelli94 commented on 2017-04-14 08:37 (UTC)

The file https://resin-production-downloads.s3.amazonaws.com/etcher/1.0.0-rc.2/Etcher-1.0.0-rc.2-linux-x64.zip doesn't exist anymore!

ams1 commented on 2017-03-20 14:48 (UTC)

@lgaggini, Done.

lgaggini commented on 2017-03-19 21:30 (UTC)

Also fuse2 should be added as dependancy: /usr/share/etcher/Etcher-1.0.0-beta.19-linux-x64.AppImage: error while loading shared libraries: libfuse.so.2: cannot open shared object file: No such file or directory

ams1 commented on 2017-02-21 11:55 (UTC)

@FadeMind, Done.

FadeMind commented on 2017-02-18 18:45 (UTC)

Please update DESKTOP file: [Desktop Entry] Type=Application Categories=System;Utility;Archiving; Exec=/usr/bin/etcher Icon=/usr/share/etcher/etcher.png Name=Etcher GenericName=Etcher Version=1.0 Keywords=iso;disk;usb;dvd; Comment=Burn images to SD cards & USB drives, safe & easy

ams1 commented on 2016-09-27 09:39 (UTC)

The required dependencies are now documented on the GitHub wiki. I've updated the package. Some of the library dependencies are probably redundant as gtk2 already depends on them, but it'll be easier to sync with the docs if they're explicit here. It's harmless anyway.

ams1 commented on 2016-08-01 08:37 (UTC)

I added the dependency on gconf. Still investigating why it's needed though.

ams1 commented on 2016-07-24 12:16 (UTC)

I added you as co-maintainer, so you can fix it before I get back, if you like.

ams1 commented on 2016-07-24 12:14 (UTC)

I'm on vacation right now, so I can't test this out, but Etcher is an AppImage so I'd expect it to not need too many dependencies.

florin_kobe commented on 2016-07-24 10:12 (UTC)

GConf should be added as a dependancy: /tmp/.mount_2qKyv5/usr/bin/etcher.wrapper /tmp/.mount_2qKyv5/usr/bin/etcher: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory