summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorK900 <me@0upti.me>2022-07-14 12:11:55 +0300
committerK900 <me@0upti.me>2022-07-14 12:18:44 +0300
commit4e02bb4922790cc9c4446ffc972b731394a14bdb (patch)
tree080ffac01135097e683d39a73133a07d3599f4e7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent1f5af608e7bab7b67b47ceafcc5668e34afaae83 (diff)
linux: enable MODULE_ALLOW_BTF_MISMATCH
Right now it looks like the BTFs are not reproducible between different builds of the same kernel, and the kernel will refuse to load modules if the BTF doesn't match. This can cause some interesting side effects when Nix uses different substituters for different parts of the kernel. This is far from ideal, and we _really_ should figure out how to actually make the BTF building consistently reproducible, but that seems more complicated, so maybe we should do this to get affected systems booting. See also: https://lore.kernel.org/bpf/YfK18x%2FXrYL4Vw8o@syu-laptop/ , where the openSUSE people ran into similar issues.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions