Package Details: itch 1:1.24.0-4

Git Clone URL: https://aur.archlinux.org/itch.git (read-only, click to copy)
Package Base: itch
Description: The best way to play itch.io games.
Upstream URL: https://github.com/itchio/itch
Licenses: MIT
Submitter: FrozenCow
Maintainer: Paragoumba
Last Packager: Paragoumba
Votes: 94
Popularity: 2.01
First Submitted: 2015-12-14 22:23
Last Updated: 2021-01-19 13:45

Latest Comments

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

HibikiTaisuna commented on 2017-11-05 16:55

@fettouhi you have to change the SHA256 checksum in PKGBUILD to 422651ae84d53c82136af8f27bb77ff37d69916cc5ddde42cdb9e54cbf193fc9

(the checksum of the github archive changed for unknown reason)

HibikiTaisuna commented on 2017-11-05 16:47

patch for PKGBUILD for new stable version (v23.4.2):

From 39ce84337e34743d023d9b0402939d22e21c56da Mon Sep 17 00:00:00 2001
From: Stefan Weiberg <stefan.weiberg@germandev.org>
Date: Sun, 5 Nov 2017 17:38:00 +0100
Subject: [PATCH 1/1] newest stable version

---
PKGBUILD | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 428e8a1..88b811f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@
# Contributor: FrozenCow <frozencow@gmail.com>

pkgname=itch
-pkgver=23.4.1
+pkgver=23.4.2
pkgrel=1
pkgdesc="The best way to play itch.io games."

@@ -17,7 +17,7 @@ install="itch.install"

# sic. - source is in itch repo, kitch is a dummy repo for canary-channel github releases
source=("https://github.com/itchio/itch/archive/v${pkgver}.tar.gz")
-sha256sums=('76b48b855bf92b9c3f26c4c370b4867b6f9c404a46d3e957ffa64b63d173c5ba')
+sha256sums=('14d3de9d327d897f119708fb6f799e5df7111e6e12d360c72953fb2628b3e43a')

[ "$CARCH" = "i686" ] && _ELECTRON_ARCH=ia32; _ITCH_ARCH=i386
[ "$CARCH" = "x86_64" ] && _ELECTRON_ARCH=x64; _ITCH_ARCH=amd64
@@ -34,7 +34,7 @@ prepare() {

build() {
cd "${srcdir}/itch-${pkgver}"
- export CI_BUILD_TAG="v23.4.1"
+ export CI_BUILD_TAG="v23.4.2"
export CI_CHANNEL="stable"

release/ci-compile.js
--
2.15.0

fettouhi commented on 2017-10-24 14:09

Can anyoone install this at the moment I get an error regarding the sha256sums.

fasterthanlime commented on 2017-08-21 11:37

A word of caution about kitch: It's currently 850+ commits ahead of the stable version, many parts of the app have been rewritten.

However, I *have* very recently changed the release scripts so it doesn't matter which version of npm is used when building kitch (it just doesn't do `npm prune` at all).

I'm hoping for a prompt release of the next version, and there's always downgrading npm as a workaround for the current version!

raneon commented on 2017-08-21 10:53

If you have issues with itch, you can try the development version called kitch. It worked fine for me.

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.