Package Details: itch 23.4.1-1

Git Clone URL: https://aur.archlinux.org/itch.git (read-only)
Package Base: itch
Description: The best way to play itch.io games.
Upstream URL: https://github.com/itchio/itch
Licenses: MIT
Submitter: FrozenCow
Maintainer: FrozenCow (vrav, fasterthanlime, josefnpat)
Last Packager: fasterthanlime
Votes: 54
Popularity: 1.389739
First Submitted: 2015-12-14 22:23
Last Updated: 2017-05-06 22:35

Latest Comments

fasterthanlime commented on 2017-07-25 08:15

@onizou I'm a native French speaker, so I'm looking over your suggestions now & approving most of them. Thanks! Note that the app has self-update for locales, so as soon as I'm done updating them, they'll appear in whatever version of the app you're currently running.

I'm also looking to submit a PR to npm to help 5.4.0 ship faster and/or find a solution that doesn't rely on "npm prune"

phunni commented on 2017-07-24 20:54

thanks - running "npm install -g npm@5.2.0" has fixed it for now.

onizou commented on 2017-07-24 20:32

Oh and since I have the opportunity: I made many suggestions to correct and improve the french translation of itch. But there seems to be too few french-speaking translators to validate them. Some have been automatically accepted, but the huge majority remains on hold.
What can I do so that they are accepted and arrive on the next version on AUR?

onizou commented on 2017-07-24 18:48

Thanks for these informations. :)

fasterthanlime commented on 2017-07-24 16:39

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.

onizou commented on 2017-07-24 15:05

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

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

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

> 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

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?

All comments