Closed 573 closed 3 years ago
It would be great if you could provide a nix expression that causes the error.
Sure.
I have
# ~/.config/nixpkgs/nix-on-droid.nix
{ pkgs, ... }:
{
home-manager.config = import ./home.nix;
}
# ~/.config/nixpkgs/home.nix
{ pkgs ? import <nixpkgs> {}, config, lib,...}:
with lib;
let
home-manager = with pkgs; writeShellScriptBin "home-manager" ''
# `toString` is required to impurely track your configuration instead of copying it to `/nix/store`
exec ${(callPackage ./home-sources.nix {}).home-manager}/bin/home-manager -f ${toString ./home.nix} $@
'';
in
{
imports = [
./program/python
];
home.packages = with pkgs; [
home-manager
];
}
as well as ~/.config/nixpkgs/home-sources.nix and ~/.config/nixpkgs/program/python/default.nix
It should be possible to have a nix-shell with that configuration using:
nix-shell -E "with import <nixpkgs> {}; mkShell { buildInputs = [ (callPackage ~/.config/nixpkgs/home-sources.nix {}).home-manager ]; }" --run "home-manager -f ~/.config/nixpkgs/home.nix switch"
Hey I'm having a lot of open tickets right now which I need to take care of. The nix expressions you're currently providing are difficult for me to assemble and to analyze since they are split apart and there is a lot of stuff in there which is not really relevant.
It would be a great help if you could already simplify it to one expression like this for example:
let
mach-nix = import (builtins.fetchGit {
url = "https://github.com/DavHau/mach-nix/";
ref = "refs/tags/2.2.2";
});
in mach-nix.mkPythonShell rec {
python = mach-nix.nixpkgs.python37;
requirements = ''
packages-triggering-the-problem
'';
}
I'm closing this for now as I cannot reproduce the error currently.
I think I did not use the _default
override in a useful manner.
When I use the
_default
for providers as inmy build says: