Lingolol

flashfoxI though it had been a while without any <a href="https://infosec.exchange/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> drama, but of course the universe provides.Guess what, telemetry in <a href="https://infosec.exchange/tags/devenv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devenv</a> is coming back. Again, it's Opt-Out, not Opt-In. The difference: this time that work is sponsored by the NixOS Foundation.<a href="https://github.com/cachix/devenv/pull/1776/files" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cachix/devenv/pull/1776/files</a><a href="https://oceansprint.org/reports/2025/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://oceansprint.org/reports/2025/</a><a href="https://infosec.exchange/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>Brought to you by <a href="https://fosstodon.org/@domenkozar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@domenkozar</a> of course.

Paul MeyerFurther, I opened a PR to add keep-sorted to the nixpkgs CI. keep-sorted is a language-agnostic formatter that sorts lines between two markers in a larger file. It will help us to get some order in the large top-level files like all-packages.nix!<a href="https://github.com/NixOS/nixpkgs/pull/391087" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/391087</a><a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>

Paul MeyerIf you want to learn more about gobuild.nix and why we need it, checkout my talk at FOSDEM this year: <a href="https://fosdem.org/2025/schedule/event/fosdem-2025-5654-go-in-the-nix-ecosystem-vulnerability-scanning-and-experiments-towards-a-next-gen-builder/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fosdem.org/2025/schedule/event/fosdem-2025-5654-go-in-the-nix-ecosystem-vulnerability-scanning-and-experiments-towards-a-next-gen-builder/</a><a href="https://infosec.exchange/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> <a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://infosec.exchange/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#golang</a> <a href="https://infosec.exchange/tags/vendoring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vendoring</a>

Paul Meyer<a href="https://infosec.exchange/tags/OceanSprint" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OceanSprint</a> 2025 is over, it was an great experience!I mostly worked on <a href="https://github.com/katexochen/gobuild.nix" rel="nofollow noopener noreferrer" target="_blank">gobuild.nix</a>, a next-generation builder for Go in nixpkgs. gobuild.nix removes vendoring for Go packages in nixpkgs, modeling the full dependency graph in Nix. Each module dependency will be its own derivation, including build cache on a module level.During the sprint, I moved gobuild.nix from linking dependency source into a vendor directory to providing a local directory that can be used as GOPROXY. This is both more versatile and simple.Together with <a href="https://chaos.social/@britter" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@britter</a> I started implementing a code generation tool that will help to package the large number of packages that will be part of the Go dependencies package set. The tool generates the Nix code for these packages, including the FOD hashes.<a href="https://infosec.exchange/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> <a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://infosec.exchange/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#golang</a> <a href="https://infosec.exchange/tags/vendoring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vendoring</a>

decafkafkThis is a serious proposal, we should actually ban and denounce determinate systems now.<a href="https://discourse.nixos.org/t/we-should-urgently-ban-and-denounce-determinate-systems/61356" rel="nofollow noopener noreferrer" target="_blank">https://discourse.nixos.org/t/we-should-urgently-ban-and-denounce-determinate-systems/61356</a> Please. <a class="hashtag" href="https://catgirl.farm/tag/nix" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a class="hashtag" href="https://catgirl.farm/tag/nixos" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a class="hashtag" href="https://catgirl.farm/tag/nixpkgs" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>

PonygolWant to help out Nixpkgs but don't know what to do? I compiled a list of still failing packages due to switching to GCC-14 in stdenv a while back. GCC changed some warning to errors in this version and lots of especially older projects fail to build now.Plenty of examples of the fix already in Nixpkgs, ideal for first time contributors.<a href="https://polygon.github.io/fix-nixpkgs-gcc14/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://polygon.github.io/fix-nixpkgs-gcc14/</a><a href="https://chaos.social/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://chaos.social/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a href="https://chaos.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>

musicmatze :rust: :nixos:Can we please remove <a href="https://hachyderm.io/@determinatesystems" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@determinatesystems</a> from the <a href="https://social.linux.pizza/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://social.linux.pizza/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> community?

Jérémy GarniauxLooks like I got a first PR merged into <a href="https://mapstodon.space/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> master, thanks to <a href="https://mathstodon.xyz/@Pol" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Pol</a> \o/<a href="https://mapstodon.space/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://mapstodon.space/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://mapstodon.space/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a>

Thomas GerbetThe latest set of GRUB2 <a href="https://social.gerbet.me/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> vulnerabilities from mid-February <a href="https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.html</a> requires **79** patches, along with some adjustments, to be applied to the latest stable tarball without breaking <a href="https://social.gerbet.me/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> tests.This does not make life easy for downstream consumers.If other distro maintainers want to take a look, I have isolated the patches so you don't have to deal with Nix: <a href="https://gist.github.com/LeSuisse/34059dd08bddc9b509097d42d3ca9109" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gist.github.com/LeSuisse/34059dd08bddc9b509097d42d3ca9109</a><a href="https://social.gerbet.me/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> PR: <a href="https://github.com/NixOS/nixpkgs/pull/383375" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/383375</a>

LEGO® Worm™The <code>firefox-bin</code> package in Nixpkgs is about to be marked as unfree because of the Terms of Use update. The new Terms of Use only apply to Mozilla's official binaries, so the <code>firefox</code> package (which is built from the official sources by Hydra) is unaffected. <a href="https://github.com/NixOS/nixpkgs/pull/385857" rel="nofollow noopener noreferrer" target="_blank">https://github.com/NixOS/nixpkgs/pull/385857</a> <a href="https://possum.city/tags/nix" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://possum.city/tags/lix" rel="nofollow noopener noreferrer" target="_blank">#lix</a> <a href="https://possum.city/tags/nixpkgs" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://possum.city/tags/nixos" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a href="https://possum.city/tags/firefox" rel="nofollow noopener noreferrer" target="_blank">#firefox</a> <a href="https://possum.city/tags/mozilla" rel="nofollow noopener noreferrer" target="_blank">#mozilla</a>

Ariel (🐿 arc)WHAAAAT<a href="https://gitlab.com/TECHNOFAB/nix-gitlab-ci" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/TECHNOFAB/nix-gitlab-ci</a><a href="https://eigenmagic.net/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> <a href="https://eigenmagic.net/tags/NixPkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixPkgs</a> <a href="https://eigenmagic.net/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://eigenmagic.net/tags/GitLabCI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLabCI</a> <a href="https://eigenmagic.net/tags/CitLabCICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CitLabCICD</a> <a href="https://eigenmagic.net/tags/CICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICD</a> <a href="https://eigenmagic.net/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://eigenmagic.net/tags/PlatformEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PlatformEngineering</a>

Benedikt Ritter (he/him)🚀 New Blog Post! 🚀I've been working on optimizing Gradle build support in nixpkgs! In my latest post, I take a deep dive into how it currently works, the limitations of the existing approach, and an optimization that improves efficiency and maintainability.Check it out here: <a href="https://britter.dev/blog/2025/02/19/nixpkgs-gradle-optimization/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://britter.dev/blog/2025/02/19/nixpkgs-gradle-optimization/</a>I’d love to hear your thoughts! Also, if your team needs Gradle or NixOS consulting, I’d be happy to help. 😊<a href="https://chaos.social/tags/Gradle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gradle</a> <a href="https://chaos.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> <a href="https://chaos.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://chaos.social/tags/BuildTooling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BuildTooling</a> <a href="https://chaos.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a>

hexa-Unfortunately <a href="https://chaos.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> currently does not seem well-equipped to resolve this conflict, due to a lack of policy and common sense seems not to be well distributed.Ultimately this is a governance issue for <a href="https://chaos.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> where the steering committee would be in a great position to limit the scope of what is acceptable behaviour.In fact, if you have an opinion on the matter, please reach out to any steering committee representative and tell them:<a href="https://github.com/NixOS/org/blob/main/doc/governance.md" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/org/blob/main/doc/governance.md</a>3/n

hexa-The <a href="https://chaos.social/tags/devenv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devenv</a> CLI does not do informed consent and neither `devenv.sh` nor `devenv.new` have a privacy policy or will tell you who runs the service and who it shares its data with.In <a href="https://chaos.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> the package was bumped to 1.4.0 after which a contributor immediately sent a follow-up PR¹ to enable `DO_NOT_TRACK=1` when wrapping the devenv binary.This was promptly reverted² by the author of devenv.🧵2/n[1] <a href="https://github.com/NixOS/nixpkgs/pull/381817" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/381817</a> [2] <a href="https://github.com/NixOS/nixpkgs/pull/381981" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/381981</a>

decafkafkI’ve noticed there is a huge fire in your bedroom, but before we can do anything I’d prefer if we opened an RFC to make sure that everyone agrees that-Oh what is that, the house burned down while we were pontificating the finer points of- Where are you going! COME BACK AND ARGUE WITH ME<a class="hashtag" href="https://catgirl.farm/tag/nix" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a class="hashtag" href="https://catgirl.farm/tag/nixos" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a class="hashtag" href="https://catgirl.farm/tag/nixpkgs" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>

musicmatze :rust: :nixos:And this, boys and girls, is why packagers of software should be different from authors of that software:<a href="https://github.com/NixOS/nixpkgs/pull/381981" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/381981</a><a href="https://social.linux.pizza/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> <a href="https://social.linux.pizza/tags/drama" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#drama</a> again.

flashfox<a href="https://hachyderm.io/@jfredett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jfredett</a> <a href="https://infosec.exchange/@oliverwiegers" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@oliverwiegers</a> .... and reverted by the author, who apparently has commit rights and does not seem to agree with community PR workflow.So we now have commercial actors in <a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> who can just push their own commercial agenda be decree.<a href="https://infosec.exchange/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://infosec.exchange/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a href="https://infosec.exchange/tags/devenv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devenv</a>

flashfox<a href="https://hachyderm.io/@jfredett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jfredett</a> <a href="https://infosec.exchange/@oliverwiegers" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@oliverwiegers</a> At least in <a href="https://infosec.exchange/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a> the telemetry seems to be of by default now<a href="https://github.com/NixOS/nixpkgs/pull/381817" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NixOS/nixpkgs/pull/381817</a><a href="https://infosec.exchange/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://infosec.exchange/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> <a href="https://infosec.exchange/tags/devenv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devenv</a>

Jérémy Garniauxe.g: if you want to package something that is not available yet in <a href="https://mapstodon.space/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>, you'll have to figure out what the dependencies of the package are, and how do you wanna declare them as inputs in the derivation you're writing. Talking about it, here's a nice memory aid about <a href="https://mapstodon.space/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> inputs: <a href="https://gist.github.com/CMCDragonkai/45359ee894bc0c7f90d562c4841117b5" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gist.github.com/CMCDragonkai/45359ee894bc0c7f90d562c4841117b5</a>

Robert Hensing<a href="https://mastodon.art/@emilychwiggy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@emilychwiggy</a> I don't pin the extensions. Missing executables can generally provided with the direnv extension.<a href="https://functional.cafe/tags/Nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nixpkgs</a> doesn't provide a mature vscode or vscodium distribution yet. Needs automated tests and more maintainers, I would guess.

Recent searches

Search options

Administered by:

Server stats:

#nixpkgs