overideScope rename

gotjoshua · April 24, 2024, 8:42am

I am getting this warning in my nixOS sys config when i do rebuild switch:

trace: warning: `overrideScope'` (from `lib.makeScope`) has been renamed to `overrideScope`.

(in a way the message is a bit comical but thats ok…)
it comes from here:

github.com

NixOS/nixpkgs/blob/e720f4ba1cf329585321eac53f503e2d031f6e40/lib/customisation.nix#L548


      
            makeScope :: (AttrSet -> ((AttrSet -> a) | Path) -> AttrSet -> a) -> (AttrSet -> AttrSet) -> scope
            ```
          */
          makeScope = newScope: f:
            let self = f self // {
                  newScope = scope: newScope (self // scope);
                  callPackage = self.newScope {};
                  overrideScope = g: makeScope newScope (extends g f);
                  # Remove after 24.11 is released.
                  overrideScope' = g: warnIf (isInOldestRelease 2311)
                    "`overrideScope'` (from `lib.makeScope`) has been renamed to `overrideScope`."
                    (makeScope newScope (extends g f));
                  packages = f;
                };
            in self;
          
          
/**
            backward compatibility with old uncurried form; deprecated
          
          

          
  # Inputs

but i don’t use overrideScope nor makeScope anywhere in my config.

How to deal with this warning?

drupol · April 24, 2024, 10:08am

Just ignore it, it’s probably coming from somewhere else, out of your files and therefore, not under your responsibility.

jtojnar · April 24, 2024, 10:26am

You can find out what is causing it by setting NIX_ABORT_ON_WARN=true environment variable and --show-trace. See the docs for lib.warn.

If you are using flakes, you will need to disable pure evaluation for the environment variable to be available in Nix. Something like the following should work:

NIX_ABORT_ON_WARN=true nix build .#nixosConfigurations.myHost.config.system.build.toplevel --option pure-eval false --show-trace

Then you should check if you have up to date version of the project that is causing the warning and, if so, report an issue against it.

gotjoshua · April 29, 2024, 8:53am

thanks, i didn’t manage to track it down, cuz flake update chased the warning away…

cheers