Package Details: runescape-launcher 2.2.11-1

Git Clone URL: https://aur.archlinux.org/runescape-launcher.git (read-only, click to copy)
Package Base: runescape-launcher
Description: RuneScape Game Client (NXT)
Upstream URL: https://www.runescape.com/
Keywords: games
Licenses: custom
Submitter: ivan_p
Maintainer: grawity
Last Packager: grawity
Votes: 52
Popularity: 0.000082
First Submitted: 2016-02-19 14:08 (UTC)
Last Updated: 2023-02-09 05:50 (UTC)

Required by (0)

Sources (4)

Pinned Comments

JagexDark commented on 2019-11-13 10:02 (UTC)

The GUI label is intentionally 2.2.4, this is related to it being a Linux-only launcher update, sorry if this causes any confusion

grawity commented on 2017-09-11 17:26 (UTC) (edited on 2020-07-02 08:45 (UTC) by grawity)

Note: It is important to keep PGP signature verification enabled, because this PKGBUILD does not verify sha256sums due to Jagex frequently releasing rebuilds with the same version number.

Don't forget to import the Jagex PGP key if installing for the first time:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-key AAC9264309E4D717441DB9527373B12CE03BEB4B

Latest Comments

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

waan commented on 2019-12-05 01:11 (UTC)

@grawit i don't think it is bug in yay, because manually importing the key does not work either. Not sure if the problem is on my side, did not had any issues with importing gpg keys in past. I even had iptables turned off when trying to import keys.

grawity commented on 2019-12-04 20:17 (UTC)

@waan if importing keys in yay doesn't work, the yay bug report page is over there ⇒ https://github.com/Jguer/yay/issues

waan commented on 2019-12-04 18:58 (UTC)

When installing runescape-launcher_2.2.6-1 with yay, importing the .gpg key fails. I have to select No when being asked to import the .gpg key, and then give argument "$ yay -S --mflags --skipinteg runescape-launcher" If not, yay will fail to build nxt. Would be nice if importing the .gpg would work again like it did before.

Eihcra commented on 2019-11-26 01:14 (UTC)

Thanks @JagexDark, perhaps you should be notifying about these crucial updates to the Flatpak and Snap repos also, before they break down too...?

JagexDark commented on 2019-11-25 11:34 (UTC)

The libssl1.1 update with launcher 2.2.6 is now live

gpc commented on 2019-11-14 06:32 (UTC)

I finally figured that you have to import the key as the user making the package, not as root...

JagexDark commented on 2019-11-13 10:02 (UTC)

The GUI label is intentionally 2.2.4, this is related to it being a Linux-only launcher update, sorry if this causes any confusion

grawity commented on 2019-11-13 07:24 (UTC) (edited on 2019-11-13 07:25 (UTC) by grawity)

It's probably just a static label that they forgot to update, because it does behave like 2.2.5 should, and in any case it's just a launcher that always downloads the latest client.

NobbZ commented on 2019-11-13 07:09 (UTC)

Thank you! At least it is starting now, though the launchers splash screen is still identifying itself as 2.2.4, is this due the upstream DEB beeing packaged wrong, or is it because of something you could fix?

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