I have to say, my automatic dependency scanner [1] for #nix packages is already working better than expected!
So far i found unused dependencies in git [2], gst-plugins-bad [3], [4], linux-pam [5], networkmanager [6] and vlc [7]. And i don't plan on stopping! All these unused dependencies cause unnecessary strain on our CI and are trivial to clean up. Some of these dependencies are even old enough to drink!
I will give a talk about the tool at @cccda this Monday in the hopes of getting more people excited for this cleanup work, and to get ideas about improving the tool.
[1] https://github.com/LordGrimmauld/nix-check-deps
[2] https://github.com/NixOS/nixpkgs/pull/391664
[3] https://github.com/NixOS/nixpkgs/pull/394242
[4] https://github.com/NixOS/nixpkgs/pull/394423
[5] https://github.com/NixOS/nixpkgs/pull/396135
[6] https://github.com/NixOS/nixpkgs/pull/395311
[7] https://github.com/NixOS/nixpkgs/pull/391226
I made an interactive treemap visualization tool for Nix derivations!
Check it out :D
@katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree
. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.
This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.
For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.
Een tribute aan de periode van 1965 tot 1975. Van Jimi Hendrix tot The Rolling Stones en van Cream tot CCR. En wat te denken van Rory Gallagher, Santana of Crosby, Stills, Nash & Young?
Veldman Vintage Project live @ The NiX 13/04/2025
#bluesmusic #livemusic #twente #livemusic_nl #nix #thenix @liveatthenix
Thank y'all for the first day of #Rejekts2025 with great talks and inspiring conversations!
I am excited that I got a spot for the #LightningTalks.
Looking forward to present you #Kubenix a tool leveraging #NixOS modules to declare #K8s workloads fully declarative.
I will also show how its #Helm integration essentially bridges the #CloudNative and #Nix ecosystem effectively, while offering additionally type safety.
See you at 18:15 in the hall #TheNash!
Short blog post on how to authenticate your NixOS deployments with comin: https://lewo.abesis.fr/posts/authenticate-nixos-deployments/
Well... I went on the deepest of dives today to fix the link error I've been tangling with while working on tigerbeetle-hs!
First, GHC passes `-lm` near the beginning of the linker flags it generates when compiling an executable. Pretty normal.
Unless you're linking a shared object file compiled from Zig.
Zig's build tool chain vendors it's own versions of libc for the various target platforms. When you call 'linkSystemLibrary2` and tell it to link `"m"` and tell Zig that's it's needed... well, it ignores you.
Zig's build tool sees that you asked to link a system library once and it links libc... and nothing else.
All of this means that if you pass `-lm` before you link the Zig shared object, you get a relink error. Because Zig helpfully provides an implementation for the libc symbol (in my case, `sin`) and the linker already has an implementation for that symbol... in libm.
It looks like Zig's tool chain doesn't include any of the GNU library paths in the RPATH of the elf header and so the linker asks you to relink the library against libm... which you can't actually do with Zig's build tools.
Trying out a hack with nix's `patchelf` to add the RPATH's into the nix store for the glibc so that the object file can declare its dependency on libm's implementation and will have to work through the community to see how we can get Zig to play nicer with systems.
Given that #Nix's `builtins.tail` is said to be inefficient and best avoided (https://noogle.dev/f/builtins/tail), what alternative method should one use to "manually iterate" through a list?
Nixpkgs' `lib.lists` doesn't care much and uses `head` and `tail`. https://github.com/NixOS/nixpkgs/blob/1b1a61b803c2fffb230262ac0c9ac0ab9dae6023/lib/lists.nix#L1176-L1177
Mark your calendars! #NixCon 2025 is set: Where: OST, Rapperswil-Jona, Switzerland
When: September 5-7, 2025 (Fri-Sun)
Tag your fellow Nix fans, spread the word, and let’s make this the best NixCon yet! More details here: https://discourse.nixos.org/t/nixcon-2025-5-7-september-in-rapperswil-jona-switzerland/62255
#Nix #NixOS
Casual #NixOS Meetup in Vienna! Join an informal NixOS meetup to chat about all things #Nix & NixOS!
April 7, 2025 |
18:00 |
GT_, Augasse 2-6, 1090 Wien
https://discourse.nixos.org/t/community-calendar/18589/195
We are hosting the 10th iteration (I forgot to toot about the previous one) of our Brussels #Nix / #NixOS / #Guix User Group Meetup next Friday, March 28th, at @HSBXL!
The lightning talks planned so far are:
- Local DNS server with CoreDNS by Hugo
- Self-hosting a Mastodon instance by @xavier and myself :)
I though it had been a while without any #NixOS drama, but of course the universe provides.
Guess what, telemetry in #devenv is coming back. Again, it's Opt-Out, not Opt-In.
The difference: this time that work is sponsored by the NixOS Foundation.
https://github.com/cachix/devenv/pull/1776/files
https://oceansprint.org/reports/2025/
Brought to you by @domenkozar of course.
I had a super nice time on Lanzarote. Big thanks to the sponsors: numtide@fosstodon.org @nixos_org @cyberus @flox @cachix and rest!
You can read the full report of #OceanSprint here: https://oceansprint.org/reports/2025/
If you want to learn more about gobuild.nix and why we need it, checkout my talk at FOSDEM this year:
https://fosdem.org/2025/schedule/event/fosdem-2025-5654-go-in-the-nix-ecosystem-vulnerability-scanning-and-experiments-towards-a-next-gen-builder/