Package Details: itch-setup-bin 1.26.0-1

Git Clone URL: https://aur.archlinux.org/itch-setup-bin.git (read-only, click to copy)
Package Base: itch-setup-bin
Description: Installer for the itch.io desktop app
Upstream URL: https://itch.io/
Licenses: MIT
Conflicts: itch, itch-setup
Provides: itch-setup
Submitter: FabioLolix
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 124
Popularity: 0.034503
First Submitted: 2022-03-13 20:08 (UTC)
Last Updated: 2022-03-13 20:08 (UTC)

Pinned Comments

FabioLolix commented on 2022-11-27 19:51 (UTC) (edited on 2022-12-10 22:38 (UTC) by FabioLolix)

https://broth.itch.ovh/

Check new versions at https://broth.itch.ovh/itch-setup/linux-amd64

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

Lumi317 commented on 2017-07-24 18:48 (UTC)

Thanks for these informations. :)

fasterthanlime commented on 2017-07-24 16:39 (UTC)

Re the "May not delete" error: it's an npm bug introduced in npm 5.3.0 - I've been following the issue closely https://github.com/npm/npm/issues/17781 but no word from the developers there yet. You might be able to work around it by running `sudo npm install -g npm@5.2.0` - to downgrade to npm@5.2.0, which doesn't have the issue. Note that pacman may complain about this later, since it'll definitely overwrite files that were installed by it. You might also be able to use the downgrader AUR package to roll back to npm 5.2.0. I'm really sorry about this, it's happening completely outside of our control and there are no easy workarounds - I'm not even confident the hard workarounds would work. The real fix is for npm 5.4.0 to ship, so we're waiting for that.

Lumi317 commented on 2017-07-24 15:05 (UTC)

Same error for me. :( Running tasks: electron:linux-x64 Running "electron:linux-x64" (electron) task Verifying property electron.linux-x64 exists in config...OK File: [no files] Options: dir="stage", name="itch", electronVersion="1.6.2", appVersion="23.4.1", prune, asar, overwrite, out="build/v23.4.1", platform="linux", arch="x64" Packaging app for platform linux x64 using electron v1.6.2 Rebuilding native dependencies Warning: Command failed: npm prune --production npm WARN The package sinon is included as both a dev and production dependency. npm ERR! May not delete: /tmp/electron-packager/linux-x64/itch-linux-x64/resources/app/node_modules/.bin npm ERR! A complete log of this run can be found in: npm ERR! /home/nizou/.npm/_logs/2017-07-24T14_53_03_256Z-debug.log Use --force to continue. Aborted due to warnings.

phunni commented on 2017-07-24 14:29 (UTC)

Fails to build for me with: Warning: Command failed: npm prune --production npm WARN The package sinon is included as both a dev and production dependency. npm ERR! May not delete: /tmp/electron-packager/linux-x64/itch-linux-x64/resources/app/node_modules/.bin npm ERR! A complete log of this run can be found in: npm ERR! /home/paul/.npm/_logs/2017-07-24T14_27_35_826Z-debug.log Use --force to continue.

fasterthanlime commented on 2017-07-17 08:11 (UTC)

Thanks for flagging the package out of date! It's true that v23.4.2 came out, and I had to skip the AUR release for that one, because of a critical npm bug that came up 3 days ago: https://github.com/npm/npm/issues/17781 I wasn't able to find a workaround in time (not for lack of trying). Note that v23.4.2 doesn't contain any changes that affect Linux (strictly macOS fixes), so you're not missing out on anything :)

fasterthanlime commented on 2017-02-07 16:23 (UTC)

> Is there any compelling reason why Grunt should re-download it I'm afraid that's just how electron-packager works - the version of electron you install via npm is more of a 'development' build, whereas the version electron-packager wants is a 'production' template it uses to generate the final application. You could always forgo the PKGBUILD and just run itch from source :) (don't forget to export NODE_ENV=production when starting it, otherwise it'll be needlessly slow)

xananax commented on 2017-02-07 15:56 (UTC) (edited on 2017-02-07 15:58 (UTC) by xananax)

I have a very slow/sketchy connection, and the build breaks on downloading electron; I have to restart it sometimes for several days in a row before I get it to compile. I have Electron installed as a package (v 1.4.15, which the version needed), but it doesn't seem grunt cares much. Is there any compelling reason why Grunt should re-download it, and is there any way to do that as a separate step through pacman/npm?

jurf commented on 2016-12-17 20:51 (UTC)

Thanks!

fasterthanlime commented on 2016-12-15 13:23 (UTC)

v22.0.0 is out, we're now using "npm shrinkwrap" to freeze dependencies, which *should* prevent random breakage in the future!

fasterthanlime commented on 2016-12-13 21:08 (UTC)

Unfortunately, reverting the package wouldn't fix it, due to the way npm works. I'm hoping to find a better fix in case other deps break eventually - but, npm freezing is pretty bad :(

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 15 Next › Last »