FS#62103 - [pycharm-community-edition] Some plugins are incorrectly marked as incompatible

Attached to Project: Community Packages
Opened by Paul Adams (crazystick) - Thursday, 21 March 2019, 17:31 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 09 September 2019, 14:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Some plugins, for example BashSupport and Markdown support (by JetBrains) cannot be installed, as they are marked as "Incompatible with the current PyCharm version."

Downloading a fresh copy of PyCharm and running it allows the installation of these plugins (using the same user configuration directory).

It looks like the PKGBUILD is messing with the build version for reasons I don't understand. JetBrains support also didn't understand it.

The bug report at GitHub has some screenshots showing the issue: https://github.com/BashSupport/BashSupport/issues/684

Steps to reproduce:

1. Install pycharm-community-edition 2018.3.5
2. Try to install BashSupport plugin
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Monday, 09 September 2019, 14:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  2019.2.1
Comment by Paul Adams (crazystick) - Thursday, 21 March 2019, 18:57 GMT
According to the developer of the BashSupport plugin, the problem is the version number of the plugin IDEA CORE (999.SNAPSHOT) which you can see in the log idea_packaged.log (the Arch packaged version). It should match the version of the product as in idea_fresh.log.

This must be caused by the patch that's being applied in this PKGBUILD
   idea_packaged.log (14.8 KiB)
   idea_fresh.log (14.7 KiB)
Comment by Frederik “Freso” S. Olesen (Freso) - Sunday, 31 March 2019, 16:24 GMT
Huh. I thought it was because pycharm-community-edition is outdated and they required the most recent version. I don't see any comment in the commit message for https://git.archlinux.org/svntogit/community.git/commit/trunk/pycharm-build.patch?h=packages/pycharm-community-edition&id=f913df111e6282475c18cf20ef6e9bbca7ea8970 why it's needed to change the `buildNumber`, but I made a patch for the patch to remove the patching of `buildNumber`. Not tried out yet.
   task-62103.patch (1.6 KiB)
Comment by Paul Adams (crazystick) - Wednesday, 10 April 2019, 12:16 GMT
I tested out that patch and unfortunately it doesn't solve the problem. It looks like the original patching of the buildNumber was doing something, as now even in the about screen, the version comes out like:

PyCharm 2018.3.5 (Community Edition)
Build #PC-183.SNAPSHOT, built on 15:34, April 9, 2019
JRE: 1.8.0_202-b26 amd64
JVM: OpenJDK 64-Bit Server VM by Oracle Corporation
Linux 5.0.2-arch1-1-ARCH

Also, the makepkg failed with `tar: ../out/pycharm-ce/artifacts/pycharmPC-183.5912.18-no-jdk.tar.gz: Cannot open: No such file or directory` as the file produced after applying your patch is pycharmPC-183.SNAPSHOT-no-jdk.tar.gz

I also tried additionally adding `sed "s/idea.build.number/build.number/g" -i python/build.xml` (kind the opposite approach to the current patching of build.xml) but that produced the same result as the current package.
Comment by Paul Adams (crazystick) - Thursday, 11 April 2019, 12:20 GMT
After replacing various things I have something that works. It doesn't seem beautiful though!
   pycharm-versions.patch (2.3 KiB)
Comment by Maxime Gauduin (Alucryd) - Monday, 09 September 2019, 14:01 GMT
Pycharm finally builds again, and I found a better solution.

Loading...