Arch Linux User Repository

I made a mistake when versioning this, and I set the package version as "2018.2" for the official release. Once the EAP was started again, and the next version was "182.3911.19", pacman/AUR helpers consider that a version downgrade (which makes sense, 182 < 2018).

The only people affected should be users who installed/upgraded phpstorm-eap when its version was "2018.2" or an RC ("2018.2-*). You can check with the command: "sudo pacman -Q phpstorm-eap".

If you have an affected version, you'll need to reinstall "phpstorm-eap":

$ sudo pacman -R phpstorm-eap phpstorm-eap-jre

$ $aurHelper -S phpstorm-eap

---

From this point forward, I will maintain the version number as the build number (182.x.x) to avoid future issues with "downgrades".

I'm stepping in as maintainer of this package (unless someone else would prefer to handle it, but I'll handle it for now).

I've updated this package to build "181.4892.97", which is currently the "stable" version of PHPStorm. I'm following @fightcookie's logic and also believe that "phpstorm-eap" should always be the most-up-to-date version fo PHPStorm.

However, @glagola notes that if the EAP is ever installed after a stable release, the expiration date stops updating (unfortunately, I read this after updating the package, of course). If that is still the case, I'll be sure not to update this package with a "stable" release in the future.

I don't use the EAP for a long time now, because I think it is worth the money for a software I use on a daily base. For a while maintaining the package was pretty straight forward. Things changed and I neither has the time, nor the patience to maintain this package anymore. Someone else may take it over. It was a nice trip.

When I launch it, I get the following error message: « This build of PhpStorm has expired. Please download a new build ... »

Last version: 173.4127.13

sha256sum: 736e95d87398a5c0e285c064201567edb672085d8a1b5fe64ee4461c19e3a2a3

@KingCrunch please update package, the license of current package (172.3757.60-1) will expire at September 10.

@fightcookie The main problem of mixing stable and EAP - for me it is licence issues. If I install EAP after stable I'll have to purge all config files of the phpstorm, cause the licence expiration date won't be updated automatically in this case.

Jetbrains provides HTTPS download for this package. Maybe you should change to HTTPS instead of HTTP? For me this helps me circumvent the corporate network security. But in general a HTTPS connection is always recommended when available.

> curl: (22) The requested URL returned error: 403 Forbidden Jetbrains remove outdated EAP packages after some time, or in this case immediately. > when the stable version is newer than the EAP release, isn't the stable version the one everyone wants to use, because EAP users always want the newest release? This package focus on the release from the early-access-programm and don't wants to be mixed up with stable release. Latter one requires a different license too. I assume that would lead to more confusing. Sorry, but I don't decide which release somebody should use.

curl: (22) The requested URL returned error: 403 Forbidden ==> ERROR: Failure while downloading http://download.jetbrains.com/webide/PhpStorm-EAP-171.4073.14.tar.gz