#Tag
I'm happy to announce there will be a Nix and NixOS devroom at FOSDEM 2026!
I'm happy to announce there will be a Nix and NixOS devroom at FOSDEM 2026!
❄️ Organizing your Nix configuration without flakes / Kylie McClain
https://somas.is/note-organizing-nix-configuration-without-flakes.html
The #nix Steering Committee election is still ongoing. If you did not cast your vote you still have a bit of time (but not much). Please make your voice heard and cast your vote. All info on how to vote: https://discourse.nixos.org/t/the-election-committee-announces-the-second-steering-committee-election/69354
The #nix Steering Committee election is still ongoing. If you did not cast your vote you still have a bit of time (but not much). Please make your voice heard and cast your vote. All info on how to vote: https://discourse.nixos.org/t/the-election-committee-announces-the-second-steering-committee-election/69354
ha, maybe for these runtime missing libs I can run nix-shell -p xorg.libXbla and run ./result/bin/my_app inside? should allow to troubleshoot faster (I haven't tested this yet)
ok now I'm stuck 😥
if I try to run my app it crashes instantly with:
> Library libxkbcommon-x11.so could not be loaded.
I've added libxkbcommon to buildInputs.
If I run $ find /nix/store/ | grep libxkbcommon-x11 , it find several instances of libxkbcommon-x11.so , for example:
/nix/store/klv07fh03501djj4q146z6pl7ywc550w-libxkbcommon-1.11.0/lib/libxkbcommon-x11.so
So I guess I have to fix the LD_LIBRARY_PATH of my package but I'm not sure how?
#nix
I'm in the process of write my second flake.nix file and so far it goes smoother than what I feared 😅 .. BUT!
I'm packaging a rust app with a gui, so needing X11 and a bunch of libX* , and I'm currently in this loop:
> nix build
[wait 10mn for cargo to build from scratch]
> ./result/bin/my_app
Error: libXbla.so not found
> [add pkgs.xorg.libXbla to buildInputs]
> repeat
Is there a way to speed this up? Can I tell nix to cache some/most of what cargo compiles? Or guess the deps quicker?
#nix
Pwning the Entire Nix Ecosystem - ptrpaws's blog 🌸 / @ptrpaws
I have an (yet another) understanding issue with #nix X) , I think I've a functional (sic) understanding of what a flake.nix is (or at least, does / provides), but on the other hand I've no idea what "regular" nix files are used for / how they are different. I have the feeling that I can split my flake.nix file into several nix files + small flake.nix "importing" them (how?), and I'm also under the impression this is not their only use, nor their main one 😊 . If someone has pointers for me <3
If you're looking for a recommendation on how to vote in the upcoming #NixOS SC (steering committee) election this guide looks pretty solid.
> The candidates are sorted by their willingness to making the NixOS community a safe and welcoming environment for people of all identities, and their ability to standing up for those values when attacked.
If you're looking for a recommendation on how to vote in the upcoming #NixOS SC (steering committee) election this guide looks pretty solid.
> The candidates are sorted by their willingness to making the NixOS community a safe and welcoming environment for people of all identities, and their ability to standing up for those values when attacked.
Recently, srid, Jon Ringer and other banned nazis have put out a voting guide. Needless to say, they advice voting for 100% fash candidates, while also making legendary comments such as "prioritizes community health over tech, BAD".
Fear not! There's now a good voting guide. Spread wide and far, folx! 
Recently, srid, Jon Ringer and other banned nazis have put out a voting guide. Needless to say, they advice voting for 100% fash candidates, while also making legendary comments such as "prioritizes community health over tech, BAD".
Fear not! There's now a good voting guide. Spread wide and far, folx!
Hey #nix people, yesterday I built my first rust project with docker image with flake and you've been very helpful to help me overcome difficulties, so thank you, but there's still so many things I'm not understanding and I can't find a lot of documentation. I've found this : https://nixos.org/manual/nixpkgs/stable/ , I've also found that for the rust part : https://ryantm.github.io/nixpkgs/languages-frameworks/rust/#rust but it presents mostly specific cases examples, where do I find the exhaustive list of options? Where is the source code of this?
@katexochen thanks, it solved that problem, now it runs \0/ ... but I can't access the service with my browser /0\ , I guess it's a purely docker issue now? I've added:
ExposedPorts = {
"8000/tcp" = {};
};
and 8000/tcp shows in docker ps and docker inspect, and that's the port the app binds to, but my browser says unable to connect on http://localhost:8000/ :'(
Back at it; in the end my problem is that cargo build fails because it can't find openssl (and pkg-config). I've tried to add:
buildInputs = [ pkgs.openssl pkgs.pkg-config ];
I've also tried with nativeBuildInputs, changed nothing.
The doc I've found ( https://nixos.org/manual/nixpkgs/stable/#compiling-rust-applications-with-cargo ) was not very helpful. Where can I find the full description of all the configuration options of buildRustPackage ? Surely there's something I'm doing wrong, but what?
ok ok I'm almost there but I really struggle to navigate the documentation 😥
My app needs an assets/ directory to function, which is in the repo I'm building. I'd like to add it to my rust package, or just to the docker image, but I fail do to either. I tried to use installPhase but doing so I've lost the binary and was unable to add it again... #nix
Ok fixed that. I had to remove the cargoLock block and add cargoHash = "" and after that the fix.1 was useful.
But now I'm back at it not building because one dep present in the workspace is missing. How to you build a single #rust executable package from a workspace with #nix ? I don't want the dep to be it's own nix package so far.
Back at it; in the end my problem is that cargo build fails because it can't find openssl (and pkg-config). I've tried to add:
buildInputs = [ pkgs.openssl pkgs.pkg-config ];
I've also tried with nativeBuildInputs, changed nothing.
The doc I've found ( https://nixos.org/manual/nixpkgs/stable/#compiling-rust-applications-with-cargo ) was not very helpful. Where can I find the full description of all the configuration options of buildRustPackage ? Surely there's something I'm doing wrong, but what?
Ok fixed that. I had to remove the cargoLock block and add cargoHash = "" and after that the fix.1 was useful.
But now I'm back at it not building because one dep present in the workspace is missing. How to you build a single #rust executable package from a workspace with #nix ? I don't want the dep to be it's own nix package so far.
👋 Hello! GNU Guix is on @hachyderm - yay!
If you haven't heard of #gnu #guix we're a free software project that's created a hosted package manager (think homebrew or flatpak) and a GNU/Linux distribution.
GNU Guix uses the functional packaging approach pioneered by #nix and adds a user-experience and system configuration system. It uses a DSL that's based on Guile Scheme. You can use it configure your home environment, dev environments or the entire system using a declarative and transactional definition.
We hope to tell people about the project and our latest news. We'd love to engage with people around #freesoftware #guile #scheme and more general #linux topics!
A space for Bonfire maintainers and contributors to communicate
