ChanServ changed the topic of #home-manager to: Support and discussion around the Home Manager project (https://github.com/nix-community/home-manager) | Logs: https://logs.nix.samueldr.com/home-manager
cole-h has quit [Quit: Goodbye]
cole-h has joined #home-manager
<pinpox> Hi, I'm trying to follow the flakes example from the README https://github.com/nix-community/home-manager#nix-flakes but my config fails to build on options set to nixpkg:
<pinpox> The option `home-manager.users.pinpox.nixpkgs' does not exist.
<pinpox> E.g. in my home-manager config: nixpkgs.config.retroarch = { enableBeetleLynx = true; }
cole-h has quit [Ping timeout: 260 seconds]
rajivr has joined #home-manager
__monty__ has joined #home-manager
s1341 has quit [Quit: Connection closed for inactivity]
patagonicus has joined #home-manager
<petrichor> Since running `nixos-rebuild switch --upgrade` yesterday, I keep getting `collision between '/nix/store/1yn854k2xhh02w1szbyrvrbfvxfj51bv-sway-1.5.1/bin/sway' and '/nix/store/sdww3sx22phli4b1mhn2asv759a6spdy-sway-1.5.1/bin/sway'`, which is preventing the build from succeeding and preventing me making any config changes at all
<petrichor> Any idea how to fix this? Is it possible that `programs.sway` and `home-manager.users.<me>.wayland.windowManager.sway` are trying to bring in different versions of the same package somehow?
<petrichor> I don't seem to have retained any channel generations for which this isn't broken, so I can't unblock myself by rolling back ☚ī¸
<siraben> Jez (he/him) 🎄: i would resolve that by removing the home-manager config
<petrichor> siraben: hmm, that does allow a new generation to be built successfully, but then of course it's one with none of my user config so lovingly constructed via home-manager
<siraben> Right, I'm not sure how to combine them, hm.
<siraben> I'm in a similar situation
ece has quit [Ping timeout: 260 seconds]
cole-h has joined #home-manager
ece has joined #home-manager
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 260 seconds]
<nicolas[m]> You have to set `wayland.windowManager.sway.package = null` if you use NixOS' `programs.sway`
<nicolas[m]> You should use either one
<nicolas[m]> `programs.sway` has the advantage of automatically adding the `wayland-session` file for Sway to be available from a login manager
<nicolas[m]> AFAIK graphical sessions cannot be specified within a user's home
<nicolas[m]> So Home Manager's Sway cannot be discovered by a login manager
kalbasit_ has joined #home-manager
kalbasit has quit [Ping timeout: 256 seconds]
srk has quit [Ping timeout: 240 seconds]
srk has joined #home-manager
kalbasit_ has quit [Ping timeout: 240 seconds]
kalbasit has joined #home-manager
kalbasit has quit [Ping timeout: 240 seconds]
kalbasit has joined #home-manager
kalbasit_ has joined #home-manager
kalbasit has quit [Ping timeout: 240 seconds]
davidtwco has quit [Read error: Connection reset by peer]
davidtwco_ has joined #home-manager
o1lo01ol1o has joined #home-manager
<petrichor> Aha, that makes a lot of sense, thanks nicolas !
o1lo01ol1o has quit [Remote host closed the connection]
<petrichor> That should probably be in the hm docs. I'll look at doing a pull request.
<petrichor> I'd assumed that hm's config couldn't install it at the system level but didn't realise it was still pulling in a potentially conflicting package.
__monty__ has quit [Quit: leaving]
justanotheruser has quit [Ping timeout: 264 seconds]
justanotheruser has joined #home-manager
justanotheruser has quit [Ping timeout: 260 seconds]