Skip to content

jetbrains: pycharm/idea unified builds; deprecate writerside & aqua#466331

Merged
MattSturgeon merged 1 commit intoNixOS:masterfrom
theCapypara:jetbrains-oss
Dec 15, 2025
Merged

jetbrains: pycharm/idea unified builds; deprecate writerside & aqua#466331
MattSturgeon merged 1 commit intoNixOS:masterfrom
theCapypara:jetbrains-oss

Conversation

@theCapypara
Copy link
Member

@theCapypara theCapypara commented Nov 29, 2025

This replaces #412971. It also relates to #426427 and fixes #412715.

  • pycharm-community-src and idea-community-src are renamed to pycharm-oss and idea-oss with a warning for the old aliases also informing users of the changes Jetbrains made. I checked with how the Open Source versions are supposed to be built, they are built just like Community was.
  • pycharm-community-bin and idea-community-bin are not updated anymore and now raise a warning
  • pycharm-professional and idea-ultimate are renamed to pycharm and idea with a warning
  • writerside and aqua now throw a warning when used, to be removed in 26.05
  • No packages are updated yet, I have prepared that for a later PR.

To be done for 26.05 (should do this shortly before next release):

  • Remove pycharm-community-src, idea-community-src, pycharm-professional, idea-ultimate
  • Remove pycharm-community-bin, idea-community-bin, remove the community entries from the ides.json and remove the pycharm-community and idea-community aliases
  • Remove writerside, aqua and their entries from the ides.json
  • Clean up other TODOs I added

@nixpkgs-ci nixpkgs-ci bot added the 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. label Dec 13, 2025
@leona-ya
Copy link
Member

IMK we can also drop the old packages now and throw a message where they can be found now. This is unstable, there is no reason to keep upstream unmaintained packages for another year. In that case a release note would be good tho.

The more interesting question is what to do with 25.11. I think the best solution would be to use the current state of this PR for that. Then we still offer supported versions to our users without forcing them to move.

I haven't yet tested this PR, but the changes in itself look good.

@theCapypara
Copy link
Member Author

theCapypara commented Dec 13, 2025

In that case I would then change the text to say "removed in 26.05" again, we merge this, backport it and then open a PR to throw for 26.05 / unstable, am I understanding correctly?

@leona-ya
Copy link
Member

That or alternatively we can do seperate PRs and just target release-25.11 with this. Both is okay imo.

@theCapypara theCapypara added the backport release-25.11 Backport PR automatically label Dec 14, 2025
@theCapypara
Copy link
Member Author

I think doing it via backport is probably the least messy solution, so I just changed the wording in here to say 26.05 and will open a follow-up PR once this is merged.

Copy link
Member

@leona-ya leona-ya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. Thank you very much :)

@leona-ya leona-ya added this pull request to the merge queue Dec 14, 2025
@leona-ya leona-ya removed this pull request from the merge queue due to a manual request Dec 14, 2025
@nixpkgs-ci nixpkgs-ci bot added 12.approvals: 3+ This PR was reviewed and approved by three or more persons. and removed 12.approvals: 2 This PR was reviewed and approved by two persons. labels Dec 14, 2025
@theCapypara
Copy link
Member Author

We decided to wait for merging #463570 first for one last update of the community-bin packages.

@MattSturgeon
Copy link
Contributor

I think this has been open long enough to gather feedback. Everyone seems happy.

Additionally, it's blocking follow-up work, so I'll merge it now.

Thanks everyone!

@MattSturgeon MattSturgeon added this pull request to the merge queue Dec 15, 2025
Merged via the queue into NixOS:master with commit da0379a Dec 15, 2025
26 of 29 checks passed
@nixpkgs-ci

This comment has been minimized.

@theCapypara
Copy link
Member Author

The backport should be doable when #470841 is merged. Do we need to create it manually then or can the bot retriggered by re-adding the label here then?

@MattSturgeon
Copy link
Contributor

Do we need to create it manually then or can the bot retriggered by re-adding the label here then?

You can do either. Removing & re-adding the label will trigger the bot again. Sometimes it's neater to create a single backport PR that cherry-picks all relevant commits from the respective master PRs.

@MattSturgeon MattSturgeon removed the backport release-25.11 Backport PR automatically label Dec 15, 2025
@theCapypara theCapypara added the backport release-25.11 Backport PR automatically label Dec 15, 2025
@nixpkgs-ci

This comment has been minimized.

@aoli-al
Copy link
Member

aoli-al commented Dec 22, 2025

nixpkgs-review result

Generated using nixpkgs-review-gha

Command: nixpkgs-review pr 466331
Commit: 2843a9ae458e2563041ffbdaa601458a95b0b0c4 (subsequent changes)
Merge: da0379a46bf0921c204666154ec4bcf4c8ebe81a

Logs: https://github.com/aoli-al/nixpkgs-review-gha/actions/runs/20436558833


aarch64-linux

❌ 2 packages failed to build:
  • jetbrains.idea-oss
  • jetbrains.pycharm-oss
✅ 2 packages built:
  • jetbrains.idea
  • jetbrains.pycharm

n0099 added a commit to n0099/nixos that referenced this pull request Dec 26, 2025
…from cachyos, revert 17fb3b0 @ desktop.nix

* rename package `idea-ultimate` to `idea` following NixOS/nixpkgs#466331 @ jetbrains.nix
@ modules

$ nix flake update .?submodules=1
$ git submodule update --remote
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 12.approvals: 3+ This PR was reviewed and approved by three or more persons. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. backport release-25.11 Backport PR automatically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jetbrains.plugins: Why was pycharm-community removed from all the plugins in plugins.json?

6 participants