I currently have webkitgtk as a buildInput for another package and whenever I try to install that package it tries to build webkitgtk from source. Not sure how to debug why though.
My current channels are the following and I believe that in this case everything should be going through the nixos channel by default.
these 3 derivations will be built:
/nix/store/bg30d01il3278s2qg5hg1pm478rd599d-webkitgtk-2.36.3.drv
/nix/store/9jmkkndiwawszgqsb3ig4khv7qpvlzy3-NetworkManager-openconnect-1.2.8.drv
/nix/store/d0idlqv2n3rmjsmjg16ic7pdmxbzviv0-binary-eater.drv
building '/nix/store/bg30d01il3278s2qg5hg1pm478rd599d-webkitgtk-2.36.3.drv'...
unpacking sources
unpacking source archive /nix/store/65kl305q2jvacnaxm05j92305ivsb3z1-webkitgtk-2.36.3.tar.xz
I eval’d webkitgtk.drvPath on every released revision of 22.05 and the last 15 revisions of unstable, for both x86_64-linux and aarch64-linux (you didn’t mention what platform you’re on), and none of them matched the /nix/store/bg30d01il3278s2qg5hg1pm478rd599d-webkitgtk-2.36.3.drv that you’re trying to build.
So I see two possibilities. 1) You have an overlay that is modifying one of its dependencies. 2) You are not using the channels you think you are, and are using something like the master or release-22.05 branches from GitHub by mistake somehow.
Sorry, I should have mentioned this. I am using x86_64-linux. Your points match what I was thinking, and I looked in hydra to see what builds were made. Noticed that none of them matched my derivation for webkitgtk. I do have a couple of overlays but don’t know how they could impact a webkitgtk dependency. Will post back after debugging more.
I dunno if this exactly would work, but something like it might point you in the right direction:
# modify this line if necessary to eval your config,
# but note that I'm trying to eval nixos, not nixpkgs
drv=$(nix-instantiate "<nixos/nixos>" -A pkgs.webkitgtk)
nix path-info --store https://cache.nixos.org $(nix-store -q --outputs $(nix-store -q --references $drv))
It should spit out complaints about the immediate dependencies of webkitgtk that aren’t on the cache.
For nix-diff to work, do I have to the derivation path built locally? One of the issues I have is building webkitgtk is an intense build job, which is why I want to rely on the cache. Tried it out in general and seems really useful.
EDIT: just read the README more carefully. Let me play with nix-instantiate.
nix-diff /nix/store/bg30d01il3278s2qg5hg1pm478rd599d-webkitgtk-2.36.3.drv /nix/store/nc6s68w808xqi61m2ksgyfzp2gcvpiry-webkitgtk-2.36.3.drv
- /nix/store/bg30d01il3278s2qg5hg1pm478rd599d-webkitgtk-2.36.3.drv:{out}
+ /nix/store/nc6s68w808xqi61m2ksgyfzp2gcvpiry-webkitgtk-2.36.3.drv:{out}
• The input derivation named `geoclue-2.5.7` differs
- /nix/store/pphfssd07i2sf1229f07nhv6bph2jbih-geoclue-2.5.7.drv:{dev}
+ /nix/store/jgfk3jfljd7871v4nsy5sgy04jyyq1vy-geoclue-2.5.7.drv:{dev}
• The input derivation named `glib-networking-2.72.0` differs
- /nix/store/0p22yapy1br5y8ykha7qzalz1gf5ngi4-glib-networking-2.72.0.drv:{out}
+ /nix/store/vdhlz9vp2zl072x2zx7q5wl5psb137mk-glib-networking-2.72.0.drv:{out}
• The input derivation named `libproxy-0.4.17` differs
- /nix/store/n37kpqvddn91wb1n87gr5pavycfwdvl0-libproxy-0.4.17.drv:{dev}
+ /nix/store/w59z91mpg6g5q1v38ad47gzfrh4760rr-libproxy-0.4.17.drv:{dev}
• The input derivation named `networkmanager-1.38.0` differs
- /nix/store/mrmfv7sdd8sqmm4637d3rf4vjyq08z0h-networkmanager-1.38.0.drv:{dev}
+ /nix/store/4xdzga5qpjpmbkfhlvz0jx7w1jfif8qj-networkmanager-1.38.0.drv:{dev}
• The input derivation named `fix-paths.patch` differs
- /nix/store/i9krwm3z9p07j6jrqrhdcyvn7ghjkrxl-fix-paths.patch.drv:{out}
+ /nix/store/jfz0kl0wvwybfi8xy1qaqxpnijv6aal6-fix-paths.patch.drv:{out}
• The set of input derivation names do not match:
- openconnect-9.01
+ openconnect-8.20
• The environments do not match:
openconnect=''
/nix/store/cdab6n9vjg2y3fmhjg6q8f5ra35jlb38-openconnect-9.01/nix/store/zjhja40j7yq7klcdb0vpi1pmzscvk1x6-openconnect-8.20
''
• Skipping environment comparison
• Skipping environment comparison
• Skipping environment comparison
• Skipping environment comparison
• Skipping environment comparison
This makes sense because I am working on some development work for openconnect. What doesn’t really make sense to me is why networkmanager is a buildInput for libproxy. Also, changing openconnect with an overlay should not impact networkmanager.
Once I disable my openconnect overlay. this behaves as expected… (sorry, I forgot about this. nix-diff is amazing)
copying path '/nix/store/nhgqm00yirr9hb7zlll0s9y4ikaik05g-webkitgtk-2.36.3-dev' from 'https://cache.nixos.org'...
openconnect shouldn’t really be an input for networkmanager tbh as well.
Thanks to both you and @ElvishJerricco. Learned quite a bit from all the comments both of you provided. His example helped me pick up nix-instantiate usage (went through the manpage too).
NetworkManager requires the openconnect program so if we want to make that feature work, the most reliable way is to patch it in the source code. If we wanted to decouple it we would need to patch NM to look for the program on PATH and then have NixOS module add it to PATH of all the relevant NM services.
In the past, I have also talked with NM maintainers about the possibility of moving the VPN dependencies to the VPN plug-ins (e.g. GNOME / NetworkManager-openconnect · GitLab) and I believe they were not against it but we still have not gotten around to it.
Can you share how you compiled just the derivations without building everything?
In my case I’m trying to do this in a flake configuration, so I feel nix-instantiate might not apply, but it should be helpful anyway, I’ve tried using nix path-info --derivation ~/.setup#laptop (nixFlakes: can't figure out nix-instantiate equivalent · Issue #3908 · NixOS/nix · GitHub) but I’m having trouble figuring out how to apply that to a flake with only nixosConfigurations
So, for flakes, to get the derivation of my system configuration I had to use:
nix path-info --derivation .#nixosConfigurations.laptop.config.system.build.toplevel, with --impure too in my case
Thanks to Patryk27
Now I’m in a place where if I do an upgrade (sudo nixos-rebuild switch --flake ${location}#${host} --upgrade --update-input nixos-hardware --update-input nixos-nvidia-vgpu --update-input home-manager --update-input nixpkgs --impure), it’ll try to rebuild webkit (and a bunch of stuff) from source.
Is there a way to check what’s in cache to see why it’s not getting it from there, or maybe prevent the upgrade of a package if it’s not yet in cache?
If you mean the hydra binary cache, that sounds like you might be tracking master or staging rather than unstable. What is your nixpkgs source? github:nixos/nixpkgs? Or a specific branch?
That looks fine at least from the nixpkgs release channel you’re tracking. It’s a big config so I can’t immediately see what else is happening, sorry to not be of more help. Godspeed!
That’s what nixpkgs-unstable (and nixos-unstable) are, or any of the nixos-23.05, 23.11, … etc releases. Those channels are only updated after hydra builds everything successfully.
Stable channels (nixos-23.05) provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after initial release. New stable channels are released every six months.
You’re on a stable channel, which is even more guaranteed to only move forward when packages are built in Hydra. It’s likely you specify an overlay of some kind which overrides a base package into a new derivation that isn’t built by Hydra, and never will be.
