I updated to 26.05 and have the problem that git authentification doesn’t work anymore.
the remote repository is hosted on a azure system.
the authentication is done via password.
when i try the error message is the same as if i typed the wrong password.
when i use nix shell to use git 2.53.0 from nixpkgs i have no problem.
any suggestion how to investigate the problem in such a way that i can write a proper bug report for nixpkgs?
It might be nixpkgs, but usually when I upgrade software and some feature stops working (as opposed to the package not being callable or immediately segfaulting+crashing), I tend to assume it’s an upstream problem and start investigating from there. If investigations suggest otherwise, then I pivot back to nixpkgs.
Spin up a VM, install the same version of git using a non-nix method, check if authentication works. If it also doesn’t, this makes it much more likely to be upstream issue.
If the VM git works and the git from nixos-26.05 doesn’t despite the same git --version, this makes it more likely that there is an issue in nixpkgs or in the specific dependency tree being pulled it. Probably first thing is to check nixpkgs to see where pkgs.git is defined and identify if any patches are being applied. Second would be something like git bisect --first-parent, using npc (a third-party tool), or manually bisecting through https://releases.nixos.org/?prefix=nixos/26.05/ and https://releases.nixos.org/?prefix=nixos/25.11/ to see where the behavior changes, then identifying what changed in the dependency closure or package definition.
Good luck!
So what password did it ask for? The remote users password or your local SSH key password?
If you use (forget this, I read that this is in the context of evaluating/building, but seems to be generic git usage)-vvvvvvvvvv for overly verbose firrhose style logging, do you see any differences?
yes you are right its a problem introduced by the latest git release not nixpkgs.
now trying to find the issue tracker of git.
I havn’t found out yet what the issue is but git from master works. so it should be fixed in the next version of git 2.55.0.