gemini-cli: add warning - #522364
Conversation
e7654b1 to
4e12afb
Compare
|
| homepage = "https://github.com/google-gemini/gemini-cli"; | ||
| license = lib.licenses.asl20; | ||
| sourceProvenance = with lib.sourceTypes; [ fromSource ]; | ||
| knownVulnerabilities = [ "gemini-cli will be deprecated and removed in a future release." ]; |
There was a problem hiding this comment.
Shoudn't we use meta.problems for this?
There was a problem hiding this comment.
Is there any "clear" guidelines ? I did not find any.
There was a problem hiding this comment.
And I can't find anything about meta.problems here: https://nixos.org/manual/nixpkgs/stable/#sec-standard-meta-attributes
There was a problem hiding this comment.
Try unstable version since you're targeting master
There was a problem hiding this comment.
Thanks !
I never noticed there was 2 version of the doc.
I've made the modification (rebased).
There was a problem hiding this comment.
meta.problems is quite new, i think we might be in the first to use it :D
There was a problem hiding this comment.
In hindsight, I think it would've been fine to land the knownVulnerabilities warning, with a FIXME comment about switching to meta.problems. I don't think using meta.problems needed to delay this PR by a month 😁
Hopefully the solution is close enough that there's no reason to do that now, though.
There was a problem hiding this comment.
@MattSturgeon well the initial pr was opened a day after my issue was raised, i thought this would have be sorted quickly, but time went by 😓
There was a problem hiding this comment.
Honestly, I stopped following Google's plans on maintaining gemini-cli vs antigravity-cli, it seems like the former won't be deprecated for a while but kept for corporate users, though e.g. home-manager renamed the gemini-cli module to antigravity-cli already nix-community/home-manager#9365
9b3708c to
9e4d592
Compare
cb784d1 to
448760a
Compare
|
There's a PR fixing CI issue, you may want to wait until it's merged |
|
Can you rebase? It should fix CI. |
Done |
|
Hmm, it still fails: > error: evaluation aborted with the following error message: 'gemini-cli is disallowed from being used within Nixpkgs, because it has certain meta.problems whose kinds are disallowed: {
> removal = {
> kind = "removal";
> message = "gemini-cli will be deprecated and removed in a future release.";
> };
> }'You've correctly updated the base branch. I've seen this kind of CI failure get fixed after #537051, but it's still stuck. Most likely we will need #537051 as a vscode extension depends on this package. |
|
Now #537051 is merged, you'll need to inspect the stack trace, to see which package is depending on gemini-cli. Once you've identified the the reverse dependency, you'll need to add a I don't think there's a consensus yet on how to phrase those "a transitive dependency of mine is marked for removal" problems, though. |
|
It's all green ! But as @taranarmo say:
Should we merge anyway ? |
|
Maybe the message should be changed to some official statement by Google, it's obviously going from the large scene (I mentioned that home-manager already merged module rename to antigravity). So it seems like kind of deprecation after all at least for non-corporate users. |
|
Something like: (see https://geminicli.com/) |
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.