rycee changed the topic of #home-manager to: Support and discussion around the Home Manager project (https://github.com/rycee/home-manager) | Logs: https://logs.nix.samueldr.com/home-manager
hmpffff has quit [Quit: nchrrrr…]
mexisme has quit [Quit: WeeChat 2.7.1]
andi- has quit [*.net *.split]
Shados has quit [*.net *.split]
philipp[m] has quit [*.net *.split]
aterius has quit [*.net *.split]
alexarice[m] has quit [*.net *.split]
simbergm has quit [*.net *.split]
benkolera has quit [*.net *.split]
{^_^} has quit [*.net *.split]
manveru has quit [*.net *.split]
philipp[m] has joined #home-manager
benkolera has joined #home-manager
Shados has joined #home-manager
manveru has joined #home-manager
andi- has joined #home-manager
aterius has joined #home-manager
{^_^} has joined #home-manager
simbergm has joined #home-manager
alexarice[m] has joined #home-manager
cole-h has quit [Quit: Goodbye]
hmpffff has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
__monty__ has joined #home-manager
voidcontext has quit [Ping timeout: 258 seconds]
voidcontext has joined #home-manager
hmpffff has joined #home-manager
klntsky has quit [Remote host closed the connection]
klntsky has joined #home-manager
c0c0 has quit [Quit: WeeChat 2.6]
likivik has joined #home-manager
Dav1d23 has joined #home-manager
likivik has quit [Ping timeout: 240 seconds]
Dav1d23 has quit [Quit: Konversation terminated!]
owenowen has joined #home-manager
owenowen has quit [Ping timeout: 265 seconds]
eraserhd has joined #home-manager
cole-h has joined #home-manager
<eraserhd> There was a way to get more debug info about which links home-manager was making, and I've forgotten it... I'm using it through nix-darwin. What was it?
<eraserhd> reason: I'm changing a file, but home-manager keeps installing the old version, and I can't figure out why (or even how).
<rycee> eraserhd: I guess you mean `--verbose`?
<eraserhd> to darwin-rebuild?
<rycee> Hmm, perhaps `export VERBOSE=1` can reach the activation script called by darwin-rebuild? Otherwise I guess you'd have to call the activation script manually with that environment variable set.
<eraserhd> hmm, I replaced .source with .text and the literal text, and it updated :/
<rycee> What did you have before?
<eraserhd> Changing that line to `home.file.".weechat/sec.conf".text = builtins.readFile ./config/sec.conf;` works.
<eraserhd> there are two changed files, and doing that changes the "read" file, but it doesn't change the other file.
<rycee> Yeah, changing `./config/sec.conf` should also change the Nix store hash so it should be updated in your home directory.
<eraserhd> No clue, but I've changed them all to readFile now, and it is working. hrmm
eraserhd has quit [Quit: WeeChat 2.8]
eraserhd has joined #home-manager
<eraserhd> well, no it didn't... I did a diff and found no changes, restarted weechat, and now there are changes?? A stuck service or something??
<rycee> Not sure. I don't know much about the darwin module and how it works. Something might have happened in the nix-darwin activation script?
<eraserhd> hmm. Well, I'm gonna reboot and see what happens.
eraserhd has quit [Quit: WeeChat 2.8]
tdeo has quit [Remote host closed the connection]
tdeo has joined #home-manager
tdeo has quit [Changing host]
tdeo has joined #home-manager
eraserhd has joined #home-manager
owenowen has joined #home-manager
owenowen has left #home-manager [#home-manager]
eraserhd has quit [Quit: WeeChat 2.8]
<energizer> is home-manager.users.energizer.nixpkgs.overlays supposed to work when i'm using the hm nixos module?
<energizer> afaict only the top-level nixpkgs.overlays actually applies, setting home-manager.users.energizer.nixpkgs.overlays doesn't seem to do anything
<energizer> specifically, i've defined some attrs in a home-manager.users.energizer.nixpkgs.overlays overlay, and i'm using those packages in home-manager.users.energizer.home.packages, but `sudo nixos-rebuild` errors because those attrs are missing from nixpkgs (ie it doesnt see the overlay)
<rycee> energizer: Do you have `home-manager.useGlobalPkgs = true` in your system configuration?
<energizer> rycee: no
<rycee> Then it should work. I'm using `nixpkgs.overlays` in some configurations I deploy to declarative containers.
<rycee> Something like `nixpkgs.overlays = [(import ./overlays/nixpkgs.nix { inherit sources; })];`
<energizer> rycee: that's definitely not happening for me. not really sure how to debug it. (maybe something about channels or NIX_PATH?)
<rycee> energizer: Hmm, is you HM configuration inside the system configuration?
<rycee> That is, do you have `home-manager.users.energizer = { … }`?
<energizer> rycee: yes
<rycee> Ah, right. Try changing it to `home-manager.users.energizer = {pkgs, ...}: { … }`
<energizer> rycee: aha. working now. i think i had an extra level of function
<energizer> thanks
<rycee> It's a bit confusing with the different pkgs, one at the system level and one at the HM level, but it's difficult to get away from it.
<energizer> my config has `imports = [./other.nix]; home-manager.users.energizer = {pkgs, ...}: {some stuff}` and other.nix has `home-manager.users.energizer = {pkgs, ...}: {other stuff}`. afaict this is working -- `some stuff` and `other stuff` get merged into my config. but i dont understand how. i would get it if the value of home-manager.users.energizer were a *set* in each of these files, but they're functions, not sets. and i thought
<energizer> functions don't get merged. how is this happening?
<energizer> infinisil: is hmModule of a type "collection of functions that will each return an attrSet and those attrSets get merged"? https://github.com/rycee/home-manager/blob/master/nixos/default.nix#L11
<energizer> i think that if yes, that'd explain how this is working
<infinisil> energizer: It's a submodule, which can either be a path, an attribute set or a function
<infinisil> Attribute sets get transformed to functions taking { ... }:
<infinisil> And paths get imported (which can then again return either an attribute set or a function)
<infinisil> This is the same behavior as `imports = [ ... ]`
<infinisil> So yeah this is a case where functions get merged together, because the type of the option is a submodule
<energizer> i see, cool
__monty__ has quit [Quit: leaving]
<dsal> How do I make sure I'm always running the last bleeding-edge version of things I specify in home-manager? (new to nix in general)