malSet has quit [Read error: Connection reset by peer]
malSet has joined #home-manager
hmpffff has joined #home-manager
hmpffff has quit [Client Quit]
hmpffff has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
<kloenk>
rycee: remove mipsle-linux from the list of supporter platforms?
hmpffff has joined #home-manager
<Dandellion>
I figured I'd try using sway but I'm a little stumped as for how I'm supposed to start it up
<Dandellion>
with i3 I think home-manager abuses xinit to "hijack" the xsession no matter what wm the displaymanager tried to start right?
<Dandellion>
but I don't think there's any way to do that with a wayland thing right?
<Dandellion>
how do you people deal with it?
<cole-h>
`exec sway`
<Dandellion>
without a dm?
<Dandellion>
just straight up tty
<cole-h>
Yes
<cole-h>
That is what sway advocates in their wiki
<Dandellion>
yeah, I just kinda didn't want to give up having a nice login screen :/
<cole-h>
I've heard that some DMs support wayland sessions, but I don't see a point since I just login and then never see TTY again
<Dandellion>
I'm not the only user, a big selling point for me and home-manager was that every user would have their own xsession and settings based entirely on what user logged in
<Dandellion>
if I log in - i3, if my girlfriend logs in - kde, and so on
<Dandellion>
I guess one could emulate it by having some logic in bashrc or something to automatically start sway/xorg if you log in on a given tty
<Dandellion>
but you still forego having a nice dm. Maybe one can replace the tty to something more dm-esque 😕
c0c0 has joined #home-manager
<NobbZ[m]>
Personally, I didn't care anymore, as my WM doesnt support switching the user while keeping the session active. That's why I just start X from a TTY and let my family use the DM login. My session lives on a separate "screen" then when family uses the computer.
<kloenk>
DamienCassou: interesting aproach to add options, but as long as it is valid nix it seems good for me. But I don't have a clue on how to use/configuar powerlien
<kloenk>
Dadellion: If you use hm to manage you sway, every user gets there own wrapped sway executable, and ther own sway config und `.config/sway/config`. so you dont have a Hijacked `.xinitrc` but you have a hijacked sway executable
<kloenk>
only `powerpc64le-linux` seems to work, but is not very good implemented in nixpkgs
<__monty__>
Ok, so looking at the firefox module the wrapped/unwrapped difference doesn't seem to apply to macOS. BUT only the share extensions path is created, not ~/Library/Application Support/Firefox and therefore no profiles either. I can't figure out why it wouldn't create them. As long as cfg.profiles isn't empty it looks like it should be.
<__monty__>
*shared extensions path
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
<__monty__>
Oh 🤦, turns out it's because of the extension I added in an overlay. I didn't fill in the addonID, hoping an error would tell me the correct one and turns out that made everything silently fail.
hmpffff has joined #home-manager
hmpffff_ has joined #home-manager
hmpffff has quit [Ping timeout: 260 seconds]
<kloenk>
rycee: also we are using pkgs.stdenv.hostPlatform, which introduces impurity and prevents cross system testing/building
hmpffff_ has quit [Quit: nchrrrr…]
<kloenk>
I'm not able to get git to evaluate on armv.*-linux. so i will just deactivat the git test for it in my branch
hmpffff has joined #home-manager
__monty__ has quit [Quit: leaving]
xourt has joined #home-manager
<xourt>
Hey all, I am currently struggling to update my home-manager configuration (first time user). I have updated all channels, nixos and also the stateVersion string in my hom.nix to 20.03 but when I hit home-manager switch, it fails and tells me to use a version <=19.09
<xourt>
Is there anything else to do when upgrading home-manager?
<alexarice[m]>
have you changed the channels on your user or on root? xourt:
<alexarice[m]>
in particular the `nix-shell '<home-manager>' -A install` bit
<xourt>
yes. Actually I started with this command because I already had import [<home-manage/nixosr>] in my configuration.nix
<xourt>
everything worked fine. That was on 19.09
<xourt>
I then upgraded the nix channels to 20.03 with sudo
<xourt>
and hit upgrade
<xourt>
I thought this would magically upgrade home-manager as well.
<alexarice[m]>
I'm slightly confused, are you running home-manager using `home-manager switch` or is it linked into your `configuration.nix`
<xourt>
I am running it with `home-manager switch` but I import it in configuration.nix
<xourt>
maybe that's where the confusion comes from.
<xourt>
The reason was that I moved my config over from `configuration.nix` into a separate folder.
<alexarice[m]>
I think you want to do one or the other
<xourt>
Maybe I'll remove it completely from `configuration.nix` and start all over again.
<xourt>
yea you are right.
<xourt>
I'll try it out!
<xourt>
Thanks for the thoughts already
<alexarice[m]>
I'm only guessing what the problem could be really
<xourt>
maybe I'll be back soon ;)
hmpffff has quit [Quit: nchrrrr…]
malSet has quit [Quit: Quit.]
malSet has joined #home-manager
MmeQuignon has joined #home-manager
xourt has quit [Remote host closed the connection]
hmpffff has joined #home-manager
evanjs has quit [Ping timeout: 256 seconds]
cjpbirkbeck has joined #home-manager
asymptotically has quit [Quit: Leaving]
evanjs has joined #home-manager
<kloenk>
xourt: The state version string is supposed to stay the same and not be changed. Both in nixpkgs and home-manager. The stateversion is ther to keep track of the state of the programms manager via nix. So if you update you postgresql11 to postgresql 12 your state would be invalid because of the new state file version. nix would still update every other software (including updates of postgresql11). You still could force nix to use postgresql12, but
<kloenk>
the automatic version would be postgresql11 because of your state version
quinn has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #home-manager
cjpbirkbeck has quit [Remote host closed the connection]