Skip to content

New package: pycharm-2026.2.3 - #62812

Open
meator wants to merge 1 commit into
void-linux:masterfrom
meator:pr/pycharm
Open

meator wants to merge 1 commit into
void-linux:masterfrom
meator:pr/pycharm

Conversation

@meator

@meator meator commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

This is a more involved change.

As described in PyCharm blogpost, Pycharm Community Edition and Pycharm Professional Edition were merged into unified PyCharm. Version 2025.1 is the last version of PyCharm Community.

Current pycharm-community Void package fails to build, because its distfile returns 404, so making some change is warranted. I also have a strong suspicion that version 2025.1 is incompatible with the currently packaged version of Python. I've been having issues with pycharm-community debugger which seem to be resolved in later versions.

The initial version of this PR is nonintrusive. It might make more sense to fully replace the pycharm-community package in a similar manner as explained in the Manual. But both packages are nonfree, so doing this correctly is not as important as if would be if it the packages were freely available in the repo.

I would have pinged the maintainer of pycharm-community and offered them maintainership of pycharm, but Felix Van der Jeugt's GitHub account no longer exists.

I cannot make reasonable changes to the pycharm-community package (like revbumping it and adding an install message imploring the user to switch to pycharm) because the distfile is dead.

I've added

	if [ "$XBPS_TARGET_MACHINE" = "x86_64" ]; then
		rm -rvf ${DESTDIR}/usr/lib/pycharm/lib/async-profiler/aarch64
	fi

newer PyCharm bundles a library which provides both aarch64 and arm64 versions. xbps-src chokes on that during shlib resolving phase, since it expects x86_64. The fact that aarch64 libraries are present could imply that pycharm could work on aarch64 (and not only on x86_64, which is the current limitation)

I did very basic testing with my Python project. I can confirm that PyCharm's debugger works now.

This PR coicidentally resolves #48245

Things that should perhaps be done

  • replace/delete/make a virtual package out of pycharm

  • figure out an update file

    I have verified that pycharm-community's update file doesn't list many versions past 2025.1. I have therefore removed it when copying pycharm-community to pycharm.

  • install message for pycharm-community?

    Kinda mutually exclusive with the first point. It was implemented, so this is no longer relevant.

Testing the changes

  • I tested the changes in this PR: YES

@Bnyro

Bnyro commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Related: #61218, the same PR but for IntelliJ IDEA. There we just removed the community and professional versions and replaced it with intellij-idea.

So perhaps it also makes more sense to remove pycharm-community-edition, given that it can't build anymore?

@meator

meator commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

Thank you for your feedback @Bnyro! I implemented changes similar to #61218.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Package request: pycharm-professional

2 participants