-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sourcetrail: 2019.3.46 -> 2020.2.43 #95530
Conversation
59e4cd6
to
2c564f0
Compare
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
3 test cases are failing. I've just disabled the checks altogether with |
I've turned Fixed 1 test (CoatiSoftware/Sourcetrail#1073) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've skimmed over the changes, generally looks okay to me. I haven't looked in much details though, you're the expert on this package after all :)
I have no experience with how java packages are managed. @NeQuissimus could you review that part?
I don't have much to say here :) I think the Java work I did is an abomination but it works OK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case I think its almost ready for merge 👍 Please squash your fixups.
These are packages required to build Sourcetrail Java support - maven-compiler-plugin 3.2 - plexus-compiler-api 2.4 - plexus-compiler-javac 2.4 - plexus-compiler-manager 2.4
260d6ee
to
8c669c7
Compare
Hmm, Python indexing broke after rebasing. Probably due to Jedi updates. |
It's likely related to 12a9a93, I don't think there's much that can be done until
|
Upstream would probably appreciate a notification, maybe open an issue? |
e549e99
to
d65c60f
Compare
It's purely a packaging issue, so I don't think upstream is exactly a right place for discussion. I brought over another copy of jedi and parso from past nixpkgs commits, and that fixed the problem quite well. I intend to remove these once it's no longer needed. |
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
Well upstream needs to add support for the newer versions of their dependencies right? They might not be aware that those new versions exist or that they are incompatible. They would probably appreciate the notification. |
The changes look good. Pleas squash the sourcetrail commits to keep a working history. |
d65c60f
to
f806d4c
Compare
squashed :-) |
Also notified upstream. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)