Hm, I can’t see anything wrong with it. Seems like a pretty straightforward setup, all in line with the manual.
I couldn’t find anything about nixpkgs = nixpkgsConfig;, but I’m sure it works as intended.
One thing you could try is have a look at the flake.lock. Maybe it’s still referring to some older commit of nixpkgs?
That being said, I’m not even sure how nixpkgs-23.05 gets to home-manager in your situation. The way you’ve set up the .follows, it would expect everything to be installed from nixpkgs-unstable. Though I’m not super familiar with home-manger, so maybe I’m missing something here.
I was able to resolve it by deleting flake.lock As a newbie, it wasn’t obvious to me that flake.lock would, well, lock the versions. But being familiar with package-lock.json for nodejs that makes sense.
Is that the correct procedure to just delete the file or should I do something more focused and not so heavy-handed?
(I hit an error with another package I was trying to install but I start another thread for that issue.)
Ah ok, in that case you can use the flag --recreate-lock-file to do basically what you did first (deleting the lockfile and downloading the newest version of everything), or you can use --update-input nixpkgs to only upgrade one input without having to re-download all the others.