jetbrains: 2025.1.1 -> 2025.1.5#419026
Merged
adamcstephens merged 5 commits intoNixOS:masterfrom Aug 2, 2025
Merged
Conversation
github-actions
bot
added
10.rebuild-darwin: 1-10
|
This doesn't build for me - nor does the pkgs.jetbrains.rider.override {
libxml2 = pkgs.runCommand "libxml2.so.2" { } ''
install -Dm555 \
${pkgs.libxml2.out}/lib/libxml2.so \
$out/lib/libxml2.so.2
'';
};Would this be worth upstreaming while you're at it, or should it be a separate PR in that case? I'm on aarch64 (Apple Silicon) for what its worth but the libxml issue doesn't seem architecture dependent. |
13 tasks
ners
changed the title
nixpkgs-ci
bot
removed
10.rebuild-darwin: 1
Contributor
|
JBassett
approved these changes
Jun 24, 2025
Contributor
|
Validated idea-ultimate with a multi module project with Kotlin, Python and Typescript modules. |
nixpkgs-ci
bot
added
the
12.approvals: 1
Contributor
|
Contributor
|
Looks like on aarch64-linux, rider & clion need On aarch64-darwin, the failure was a local failure (No space left on device) caused by trying to build too much stuff in a github actions runner, so it is possible the build would've succeeded if there was more disk space. |
Contributor
|
Probably better to use patchelf instead like some existing usages? The following has been working for me on aarch64-linux: jetbrains-clion = prev.jetbrains.clion.overrideAttrs (old: {
postFixup = ''
${old.postFixup}
patchelf --replace-needed libxml2.so.2 libxml2.so $out/clion/bin/lldb/linux/*/lib/liblldb.so
'';
});
jetbrains-rust-rover = prev.jetbrains.rust-rover.overrideAttrs (old: {
postFixup = ''
${old.postFixup}
patchelf --replace-needed libxml2.so.2 libxml2.so $out/rust-rover/bin/lldb/linux/*/lib/liblldb.so
'';
}); |
Member
Author
|
@sdht0 thanks for the tip. I was able to easily add another |
Member
|
theCapypara
suggested changes
Jul 1, 2025
MattSturgeon
reviewed
Jul 1, 2025
Member
|
Note for future me and comitters: |
13 tasks
Member
|
As I understood it the solution in this PR has some issue with JCEF, but the other PR (#425529) has other issues. I see there is discussion going on and comparing it with the solution in this PR already. There is also #426285 that is also trying to fix this issue. @ners Could you also have a look at those PRs and compare it with your solution and maybe give your opinions as well? In any case I think all fixes related to jetbrains-jdk should go there first and that be merged first, then we continue here IMO. I'm unfortunately not at all experienced with Java or really understand the changes that broke the jetbrains-jdk, so I can't really give a good opinion here myself on what is the best way to deal with these issues. As for the discontinued IDEs, I've made a new issue as a reminder (#426427), if somebody has time feel free to open a PR, otherwise I'll do it soon ™️ |
Contributor
|
Contributor
|
No idea if this helps, but I've been using this for a week or so now and it seems perfectly stable (aarch64-darwin). |
nixpkgs-ci
bot
added
the
2.status: merge conflict
Contributor
|
Just a heads up that new versions of IDEs are out (Ultimate 2025.1.4.1) so it'd be great to re-run the update script before this merges. |
nixpkgs-ci
bot
removed
the
2.status: merge conflict
Contributor
|
theCapypara
suggested changes
Jul 28, 2025
Member
theCapypara
left a comment
theCapypara
left a comment
There was a problem hiding this comment.
I'm getting the same build failures unfortunately.
jetbrains.clion: 2025.1.2 -> 2025.1.4 jetbrains.dataspell: 2025.1.1 -> 2025.1.2.1 jetbrains.goland: 2025.1.2 -> 2025.1.4 jetbrains.idea-community: 2025.1.2 -> 2025.1.4.1 jetbrains.idea-ultimate: 2025.1.2 -> 2025.1.4.1 jetbrains.phpstorm: 2025.1.2 -> 2025.1.4.1 jetbrains.pycharm-community: 2025.1.2 -> 2025.1.3.1 jetbrains.pycharm-professional: 2025.1.2 -> 2025.1.3.1 jetbrains.rider: 2025.1.2 -> 2025.1.4 jetbrains.ruby-mine: 2025.1.2 -> 2025.1.4.1 jetbrains.rust-rover: 2025.1.3 -> 2025.1.5 jetbrains.webstorm: 2025.1.2 -> 2025.1.4.1
Contributor
|
Tested |
Contributor
|
Contributor
|
Also tested |
Contributor
|
Member
|
theCapypara
approved these changes
Jul 29, 2025
Member
theCapypara
left a comment
theCapypara
left a comment
There was a problem hiding this comment.
Thanks ners! In general this good to merge for me now, however I'm not sure if we have a plan on how to proceed with the -src build errors on aarch64. #425814 is closed now, is there a follow-up PR for that? I'm guessing the -src builds are broken on unstable too and it's unrelated to this PR - does somebody know or should we re-check that before merging?
Member
|
The aarch64 build failure should be addressed by #430439 |
13 tasks
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Things done
Fixes #425328
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.