ixgbevf: Suspected impurity

[nh2]

Issue description

When building a nixops deployment including a boot.kernelPatches entry and dependent packages with nix on Ubuntu, I got this build failure:

patching script interpreter paths in /nix/store/zfwsjjlpldmp9ldfi2sz1w1rizw4z5j8-ena-20160629-4.9.38
  INSTALL /run/user/1000/nix-build-ixgbevf-4.0.3-4.9.38.drv-0/ixgbevf-4.0.3/src/ixgbevf.ko
  DEPMOD  4.9.38
make[1]: Leaving directory '/nix/store/bppdvmzixf5ah6fcgqalh1vc1mf3iw38-linux-4.9.38-dev/lib/modules/4.9.38/build'
Running depmod...
depmod: FATAL: could not load /boot/System.map-4.10.0-33-generic: Permission denied
make: *** [Makefile:108: install] Error 1
builder for ‘/nix/store/2by75pkrgbkcaf78a7mcjr5g5ni7v8ss-ixgbevf-4.0.3-4.9.38.drv’ failed with exit code 2
cannot build derivation ‘/nix/store/w49plg2fbbv5705jprjfzibbry6zsw8k-kernel-modules.drv’: 1 dependencies couldn't be built

It's trying to do something with /boot/System.map-4.10.0-33-generic, which seems like an impurity.

CC @fpletz @edolstra @NeQuissimus because you have commits on ixgbevf.

Steps to reproduce

Build with a Linux kernel patch (boot.kernelPatches); for me that is

boot.kernelPatches = [
          { name = "fuse-larger-readdir"; patch = ./0001-WIP-fuse-Use-32-pages-for-fuse_readdir-instead-of-on.patch; }
        ];

with that patch being this commit.

Technical details

• System: Ubuntu 16.04
• Nix version: 1.11.14
• Nixpkgs version: ccb5642
• Sandboxing enabled: no

[nh2]

I worked around it on Ubuntu with sudo mv /boot2 /boot -- just very important to undo that once the build is done, otherwise the system won't boot any more.

I suspect that hydra's sandboxing hides this issue.

[nh2]

And I suspect that what it's doing is some kind of autodetection, for what installed kernels it has to configure itself or something like that.

[copumpkin]

I think I've seen this too

[3noch]

Any hope of actually fixing this? If it's some autodetection I'm guessing it affects multiple packages.

[stale]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.