home.social

#nixos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nixos, aggregated by home.social.

  1. @Le_suisse @devalot Thanks for that. Am having this with which I need to fix as even my nixpkgs unstable does not have some CVEs fixed. I am feeling this strongly because I am finding the FOSS nixos Sysyphus "lifestyle" has a high DIY dev / webmaster / sys admin time overhead which is a slow learning process & starting to make my worry my remaining time on Earth might be better spent. Is there a magic solution like a safe part that is offered by each package ?

  2. I just started exploring NixOS. I'm not sure if I opened a can of worms or a new passion.

    #nixos #linux #learning #tech

  3. I just started exploring NixOS. I'm not sure if I opened a can of worms or a new passion.

    #nixos #linux #learning #tech

  4. I just started exploring NixOS. I'm not sure if I opened a can of worms or a new passion.

    #nixos #linux #learning #tech

  5. I just started exploring NixOS. I'm not sure if I opened a can of worms or a new passion.

    #nixos #linux #learning #tech

  6. I just started exploring NixOS. I'm not sure if I opened a can of worms or a new passion.

    #nixos #linux #learning #tech

  7. RE: social.gerbet.me/@nixpkgssecur

    What a mess. #NixOS 26.05 uses #Immich 2.x which has a major security vulnerability. The fix won't be backported to 2.x so everyone has to upgrade to 3.x from nixpkgs-unstable. Good thing we have overlays.

    How are other distros dealing with this?

  8. RE: social.gerbet.me/@nixpkgssecur

    What a mess. #NixOS 26.05 uses #Immich 2.x which has a major security vulnerability. The fix won't be backported to 2.x so everyone has to upgrade to 3.x from nixpkgs-unstable. Good thing we have overlays.

    How are other distros dealing with this?

  9. RE: social.gerbet.me/@nixpkgssecur

    What a mess. #NixOS 26.05 uses #Immich 2.x which has a major security vulnerability. The fix won't be backported to 2.x so everyone has to upgrade to 3.x from nixpkgs-unstable. Good thing we have overlays.

    How are other distros dealing with this?

  10. RE: social.gerbet.me/@nixpkgssecur

    What a mess. #NixOS 26.05 uses #Immich 2.x which has a major security vulnerability. The fix won't be backported to 2.x so everyone has to upgrade to 3.x from nixpkgs-unstable. Good thing we have overlays.

    How are other distros dealing with this?

  11. RE: social.gerbet.me/@nixpkgssecur

    What a mess. #NixOS 26.05 uses #Immich 2.x which has a major security vulnerability. The fix won't be backported to 2.x so everyone has to upgrade to 3.x from nixpkgs-unstable. Good thing we have overlays.

    How are other distros dealing with this?

  12. I had to boot my fp5 into android to get touchscreen working, so took a detour via sailfishos. It sure is a weird and interesting os. Now thinging about being able to run oss sailfishos apps on mainline qt6 for instance #postmarkos or #nixos

  13. I had to boot my fp5 into android to get touchscreen working, so took a detour via sailfishos. It sure is a weird and interesting os. Now thinging about being able to run oss sailfishos apps on mainline qt6 for instance #postmarkos or #nixos

  14. I had to boot my fp5 into android to get touchscreen working, so took a detour via sailfishos. It sure is a weird and interesting os. Now thinging about being able to run oss sailfishos apps on mainline qt6 for instance or

  15. I had to boot my fp5 into android to get touchscreen working, so took a detour via sailfishos. It sure is a weird and interesting os. Now thinging about being able to run oss sailfishos apps on mainline qt6 for instance #postmarkos or #nixos

  16. I had to boot my fp5 into android to get touchscreen working, so took a detour via sailfishos. It sure is a weird and interesting os. Now thinging about being able to run oss sailfishos apps on mainline qt6 for instance #postmarkos or #nixos

  17. to NixOS 26.11 “Zokor” Exact build: 26.11.20260902.3ed67ec
    seems to have made some app (yet to be identified) suddenly demand my Using LUKS2 Anyone else get this?

  18. #nixos #upgrade to NixOS 26.11 “Zokor” Exact build: 26.11.20260902.3ed67ec
    seems to have made some app (yet to be identified) suddenly demand my #gnome #keyring #nixos26 Using LUKS2 #LUKS Anyone else get this? #gnome50

  19. #nixos #upgrade to NixOS 26.11 “Zokor” Exact build: 26.11.20260902.3ed67ec
    seems to have made some app (yet to be identified) suddenly demand my #gnome #keyring #nixos26 Using LUKS2 #LUKS Anyone else get this? #gnome50

  20. #nixos #upgrade to NixOS 26.11 “Zokor” Exact build: 26.11.20260902.3ed67ec
    seems to have made some app (yet to be identified) suddenly demand my #gnome #keyring #nixos26 Using LUKS2 #LUKS Anyone else get this? #gnome50

  21. #nixos #upgrade to NixOS 26.11 “Zokor” Exact build: 26.11.20260902.3ed67ec
    seems to have made some app (yet to be identified) suddenly demand my #gnome #keyring #nixos26 Using LUKS2 #LUKS Anyone else get this? #gnome50

  22. Bitwarden is... fine? It certainly doesn't have the polish of 1Password, but it is functional and for now (🙏) not funding fascists, and so on that basis, is infinitely better.

    I may look into self-hosting my vault with VaultWarden at some point, but for now this gets things moving.

    If anyone knows how to set up SSH key signing and ssh-agent on #NixOS with #Bitwarden, please point me to any relevant links. That's probably this afternoon's task.

  23. Bitwarden is... fine? It certainly doesn't have the polish of 1Password, but it is functional and for now (🙏) not funding fascists, and so on that basis, is infinitely better.

    I may look into self-hosting my vault with VaultWarden at some point, but for now this gets things moving.

    If anyone knows how to set up SSH key signing and ssh-agent on #NixOS with #Bitwarden, please point me to any relevant links. That's probably this afternoon's task.

  24. Bitwarden is... fine? It certainly doesn't have the polish of 1Password, but it is functional and for now (🙏) not funding fascists, and so on that basis, is infinitely better.

    I may look into self-hosting my vault with VaultWarden at some point, but for now this gets things moving.

    If anyone knows how to set up SSH key signing and ssh-agent on #NixOS with #Bitwarden, please point me to any relevant links. That's probably this afternoon's task.

  25. Bitwarden is... fine? It certainly doesn't have the polish of 1Password, but it is functional and for now (🙏) not funding fascists, and so on that basis, is infinitely better.

    I may look into self-hosting my vault with VaultWarden at some point, but for now this gets things moving.

    If anyone knows how to set up SSH key signing and ssh-agent on #NixOS with #Bitwarden, please point me to any relevant links. That's probably this afternoon's task.

  26. Bitwarden is... fine? It certainly doesn't have the polish of 1Password, but it is functional and for now (🙏) not funding fascists, and so on that basis, is infinitely better.

    I may look into self-hosting my vault with VaultWarden at some point, but for now this gets things moving.

    If anyone knows how to set up SSH key signing and ssh-agent on #NixOS with #Bitwarden, please point me to any relevant links. That's probably this afternoon's task.

  27. If I need 2 LLMs to update my #nixos #flake #nixpkgs in view of the cascade of problems caused, am I doing anything other than replacing dependency on reliable Apple-like bit tech infrastructure with dependency on having internet & 2 #LLM subscriptions? It might feel like computing & home-labbing & sovereign tech, but is just a mirage. Is the final frontier in my setup: only use a self-hosted LLM to do my #nixos maintenance even if it is inferior, to make myself resilient & free & learn again?

  28. If I need 2 LLMs to update my #nixos #flake #nixpkgs in view of the cascade of problems caused, am I doing anything other than replacing dependency on reliable Apple-like bit tech infrastructure with dependency on having internet & 2 #LLM subscriptions? It might feel like computing & home-labbing & sovereign tech, but is just a mirage. Is the final frontier in my setup: only use a self-hosted LLM to do my #nixos maintenance even if it is inferior, to make myself resilient & free & learn again?

  29. If I need 2 LLMs to update my #nixos #flake #nixpkgs in view of the cascade of problems caused, am I doing anything other than replacing dependency on reliable Apple-like bit tech infrastructure with dependency on having internet & 2 #LLM subscriptions? It might feel like computing & home-labbing & sovereign tech, but is just a mirage. Is the final frontier in my setup: only use a self-hosted LLM to do my #nixos maintenance even if it is inferior, to make myself resilient & free & learn again?

  30. If I need 2 LLMs to update my #nixos #flake #nixpkgs in view of the cascade of problems caused, am I doing anything other than replacing dependency on reliable Apple-like bit tech infrastructure with dependency on having internet & 2 #LLM subscriptions? It might feel like computing & home-labbing & sovereign tech, but is just a mirage. Is the final frontier in my setup: only use a self-hosted LLM to do my #nixos maintenance even if it is inferior, to make myself resilient & free & learn again?

  31. If I need 2 LLMs to update my in view of the cascade of problems caused, am I doing anything other than replacing dependency on reliable Apple-like bit tech infrastructure with dependency on having internet & 2 subscriptions? It might feel like computing & home-labbing & sovereign tech, but is just a mirage. Is the final frontier in my setup: only use a self-hosted LLM to do my maintenance even if it is inferior, to make myself resilient & free & learn again?

  32. My question above forgot to mention that the strict and machine wide, build checks of do expose dependency hell issues in a coherent way and fixing stuff with LLM help seems like a healthy normal computer hygiene task. Especially efficient is the LLM's ability to find solutions in the on-line docs automatically. Seems better that these issues happen before one actually seeks to run the apps in question. The LLM use might be (/is) causing comprehension rot on my side. But saves days.

  33. My question above forgot to mention that the strict and machine wide, build checks of #nix #nixos do expose dependency hell issues in a coherent way and fixing stuff with LLM help seems like a healthy normal computer hygiene task. Especially efficient is the LLM's ability to find solutions in the on-line docs automatically. Seems better that these issues happen before one actually seeks to run the apps in question. The LLM use might be (/is) causing comprehension rot on my side. But saves days.

  34. My question above forgot to mention that the strict and machine wide, build checks of #nix #nixos do expose dependency hell issues in a coherent way and fixing stuff with LLM help seems like a healthy normal computer hygiene task. Especially efficient is the LLM's ability to find solutions in the on-line docs automatically. Seems better that these issues happen before one actually seeks to run the apps in question. The LLM use might be (/is) causing comprehension rot on my side. But saves days.

  35. My question above forgot to mention that the strict and machine wide, build checks of #nix #nixos do expose dependency hell issues in a coherent way and fixing stuff with LLM help seems like a healthy normal computer hygiene task. Especially efficient is the LLM's ability to find solutions in the on-line docs automatically. Seems better that these issues happen before one actually seeks to run the apps in question. The LLM use might be (/is) causing comprehension rot on my side. But saves days.

  36. My question above forgot to mention that the strict and machine wide, build checks of #nix #nixos do expose dependency hell issues in a coherent way and fixing stuff with LLM help seems like a healthy normal computer hygiene task. Especially efficient is the LLM's ability to find solutions in the on-line docs automatically. Seems better that these issues happen before one actually seeks to run the apps in question. The LLM use might be (/is) causing comprehension rot on my side. But saves days.

  37. Updating revealed a download 403 error and required an update of my which in its inimitable way caused a chain reaction of problems with my flake including an insoluble package change requiring me to keep a local copy of the old code component in my flake to make it build a home-made tunneling app. Am I doing this wrong? Or is this just the way things are in and maintenance like this of packages is just inevitable work one has to do periodically?

  38. Updating #atuin revealed a #rustcrates #curl download 403 error and required an update of my #nixpkgs which in its inimitable way caused a chain reaction of problems with my flake including an insoluble #i2p package change requiring me to keep a local copy of the old code component in my flake to make it build a home-made tunneling app. Am I doing this wrong? Or is this just the way things are in #nixos and maintenance like this of packages is just inevitable work one has to do periodically?

  39. Updating #atuin revealed a #rustcrates #curl download 403 error and required an update of my #nixpkgs which in its inimitable way caused a chain reaction of problems with my flake including an insoluble #i2p package change requiring me to keep a local copy of the old code component in my flake to make it build a home-made tunneling app. Am I doing this wrong? Or is this just the way things are in #nixos and maintenance like this of packages is just inevitable work one has to do periodically?

  40. Updating #atuin revealed a #rustcrates #curl download 403 error and required an update of my #nixpkgs which in its inimitable way caused a chain reaction of problems with my flake including an insoluble #i2p package change requiring me to keep a local copy of the old code component in my flake to make it build a home-made tunneling app. Am I doing this wrong? Or is this just the way things are in #nixos and maintenance like this of packages is just inevitable work one has to do periodically?

  41. Updating #atuin revealed a #rustcrates #curl download 403 error and required an update of my #nixpkgs which in its inimitable way caused a chain reaction of problems with my flake including an insoluble #i2p package change requiring me to keep a local copy of the old code component in my flake to make it build a home-made tunneling app. Am I doing this wrong? Or is this just the way things are in #nixos and maintenance like this of packages is just inevitable work one has to do periodically?

  42. I've now made it a habit to turn on basic telemetry on new #Linux installs. These people won't use that data for advertising, but _actually_ improving the product. Let them know I put #Kinoite on a #Chromebook, #NixOS on a MacBook and #ArchLinux on a Surface Hub (that last one wasn't actually me).
    The Year of the Linux Desktop is NOW, we just don't know, because we've lost all trust in telemetry.

  43. I've now made it a habit to turn on basic telemetry on new #Linux installs. These people won't use that data for advertising, but _actually_ improving the product. Let them know I put #Kinoite on a #Chromebook, #NixOS on a MacBook and #ArchLinux on a Surface Hub (that last one wasn't actually me).
    The Year of the Linux Desktop is NOW, we just don't know, because we've lost all trust in telemetry.

  44. I've now made it a habit to turn on basic telemetry on new #Linux installs. These people won't use that data for advertising, but _actually_ improving the product. Let them know I put #Kinoite on a #Chromebook, #NixOS on a MacBook and #ArchLinux on a Surface Hub (that last one wasn't actually me).
    The Year of the Linux Desktop is NOW, we just don't know, because we've lost all trust in telemetry.

  45. I've now made it a habit to turn on basic telemetry on new #Linux installs. These people won't use that data for advertising, but _actually_ improving the product. Let them know I put #Kinoite on a #Chromebook, #NixOS on a MacBook and #ArchLinux on a Surface Hub (that last one wasn't actually me).
    The Year of the Linux Desktop is NOW, we just don't know, because we've lost all trust in telemetry.

  46. I've now made it a habit to turn on basic telemetry on new #Linux installs. These people won't use that data for advertising, but _actually_ improving the product. Let them know I put #Kinoite on a #Chromebook, #NixOS on a MacBook and #ArchLinux on a Surface Hub (that last one wasn't actually me).
    The Year of the Linux Desktop is NOW, we just don't know, because we've lost all trust in telemetry.

  47. *SIGH*

    With Debian's "come on, come all" AI decision, I am once again looking for a #distro

    Fedora is out, Ubuntu has been out since at least 22.04, and I'm not too fond of Arch-based distros, since I've had two installs nuked by normal regular updates (caused by Arch themselves).

    Maybe I try #NixOS again? Last time it blew up about 30 minutes after the install, while dealing with GNOME Extensions.

    @AerynOS and @stillhq are two options I'll look into, but both are still not final versions, and StillOS in particular is likely too "stable" (aka using older packages) for my normal use (which includes gaming). Not to mention it's ultimately a Fedora derivative, so...

    Suggestions welcome. I prefer #GNOME as a DE, btw. OK with Flatpaks and Appimages, and while I can eventually find my way around a terminal, I prefer using the GUI.

    #linux

  48. *SIGH*

    With Debian's "come on, come all" AI decision, I am once again looking for a #distro

    Fedora is out, Ubuntu has been out since at least 22.04, and I'm not too fond of Arch-based distros, since I've had two installs nuked by normal regular updates (caused by Arch themselves).

    Maybe I try #NixOS again? Last time it blew up about 30 minutes after the install, while dealing with GNOME Extensions.

    @AerynOS and @stillhq are two options I'll look into, but both are still not final versions, and StillOS in particular is likely too "stable" (aka using older packages) for my normal use (which includes gaming). Not to mention it's ultimately a Fedora derivative, so...

    Suggestions welcome. I prefer #GNOME as a DE, btw. OK with Flatpaks and Appimages, and while I can eventually find my way around a terminal, I prefer using the GUI.

    #linux

  49. *SIGH*

    With Debian's "come on, come all" AI decision, I am once again looking for a #distro

    Fedora is out, Ubuntu has been out since at least 22.04, and I'm not too fond of Arch-based distros, since I've had two installs nuked by normal regular updates (caused by Arch themselves).

    Maybe I try #NixOS again? Last time it blew up about 30 minutes after the install, while dealing with GNOME Extensions.

    @AerynOS and @stillhq are two options I'll look into, but both are still not final versions, and StillOS in particular is likely too "stable" (aka using older packages) for my normal use (which includes gaming). Not to mention it's ultimately a Fedora derivative, so...

    Suggestions welcome. I prefer #GNOME as a DE, btw. OK with Flatpaks and Appimages, and while I can eventually find my way around a terminal, I prefer using the GUI.

    #linux

  50. *SIGH*

    With Debian's "come on, come all" AI decision, I am once again looking for a #distro

    Fedora is out, Ubuntu has been out since at least 22.04, and I'm not too fond of Arch-based distros, since I've had two installs nuked by normal regular updates (caused by Arch themselves).

    Maybe I try #NixOS again? Last time it blew up about 30 minutes after the install, while dealing with GNOME Extensions.

    @AerynOS and @stillhq are two options I'll look into, but both are still not final versions, and StillOS in particular is likely too "stable" (aka using older packages) for my normal use (which includes gaming). Not to mention it's ultimately a Fedora derivative, so...

    Suggestions welcome. I prefer #GNOME as a DE, btw. OK with Flatpaks and Appimages, and while I can eventually find my way around a terminal, I prefer using the GUI.

    #linux