-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
ycmd: unstable-2023-11-06 -> unstable-2025-06-16 #430772
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
base: master
Are you sure you want to change the base?
Conversation
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.
Moin and welcome to Nixpkgs. This PR of yours must be divided in 3 commits (the following aren't title examples btw):
- version bump + dependencies
- new maintainer entry
- add yourself to the package maintainers
Any other edit should be amended to/squashed with its respective commit. You can force-push the resulting commits into the branch without closing the PR.
Thanks for the rapid response! I've got the commit history adjusted as instructed, titles be based on examples found in commit history, and have corrected the If there be any other mistakes I've made, then please do call me out on 'em! |
Nah, you're good now. Just rebase onto a fresher master commit and resolve conflicts |
Woot! I think I got it sorted then, though probably best to not trust my thinking just yet,,, rebasing with conflicts ain't always a clean process x-) |
|
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.
Approved automatically following the successful run of nixpkgs-review
.
these messages were autogenerated by Actions, which I ran before writing the latest comment. the said comment stays in power btw
d1e8c8a
to
1fb49a8
Compare
Update `version`, `rev`, and `sha256` because why not update if also fixing dependency renaming stuff. Add `legacy-cgi` due to breaking changes in Python updates; - https://pypi.org/project/legacy-cgi/ - https://peps.python.org/pep-0594/#deprecated-modules - https://peps.python.org/pep-0594/#cgi TLDR: `cgi` was deprecated in version `3.11` and aimed to be removed in `3.12` of Python due to; > “[...] designed poorly and are now near-impossible to fix (`cgi`) > [...]” Remove `disable` attribute at request of @SuperSandro2000 because Python2 is EOL Add symbolic link to address Issue NixOS#429485 with YouCompleteMe Vim plugin, however, beware there are _opportunities_ for future bug reports to be opened because of `ycmd` and YouCompleteMe version de-sync. Add `longDescription` with notes about YouCompleteMe errors when run-time and compile-time Python interpreters do not match.
Quick check-in with y'all, is there anything I need to do on my end to ensure things are easy to review? |
|
It was discovered, while struggling with the YouCompleteMe plugin/package Issue, that sometime within the past two years the Python team made good on threats to remove
cgi
from the standard library.This set of changes adds
legacy-cgi
to thebuildInputs
because theycmd
package needscgi
and, because I was already doing stuff, I updated therev
,sha256
, andversion
attributes too ;-)Things done
passthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.Add a 👍 reaction to pull requests you find important.