Nix Package Manager development | 858 Members | |
| For people hacking on Nix: https://github.com/NixOS/nix Nix maintainers can be reached here. | 184 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Nov 2025 | ||
coverity is looking for a cov-int directory with all the files from the directory and will fail very late if it doesn't match up. | 15:21:37 | |
*
coverity is looking for a cov-int directory with all the files from the directory and will fail very late if it doesn't match up. | 15:22:02 | |
*
coverity is looking for a cov-int directory with all the files from the directory and will fail very late if it doesn't match up. | 15:22:13 | |
This inside a nix develop shell? | 15:23:22 | |
| yes. | 15:23:33 | |
| I did run meson configure before. | 15:23:40 | |
| * | 15:24:51 | |
| let me try from Linux | 15:24:58 | |
| it's going! | 15:49:54 | |
| Last Build Status: In-queue. Your build is in the queue to be analyzed. There are 99 builds ahead of it. | 16:12:51 | |
| From past experience, it will take a long while :P | 16:13:11 | |
Sergei Zimmerman (xokdvium): do you think instead of doing <"....."> we can use custom string literals? | 19:33:01 | |
| that seems a little bit less stressful on the templating :) | 19:33:16 | |
| hmm, seems to be working! | 19:47:38 | |
ah it was because auto not auto & | 20:00:02 | |
| OK got it! | 20:15:42 | |
and I found that deleting the destructor will make auto instead of auto & a compile failure, yay! | 20:16:03 | |
| i've never been quite sure - what's the support status of statically linked nix? it's something i've found genuinely incredibly convenient... but the only i know to way to download one is to dig from hydra which seems not ideal | 20:50:57 | |
| * i've never been quite sure - what's the support status of statically linked nix? it's something i've found genuinely incredibly convenient... but the only way i know to download one is to dig from hydra which seems not ideal | 20:51:11 | |
curl -o nix https://hydra.nixos.org/job/nix/master/buildStatic.nix-cli.x86_64-linux/latest/download/1 feels like something i should not be "shipping to prod" so to speak | 20:51:55 | |
| it regularly fails to build on Hydra fwiw | 20:52:00 | |
| on nix hydra or nixpkgs hydra? | 20:52:23 | |
| latter, but if they differ I assume only due to former's Nixpkgs lagging behind | 20:53:09 | |
| hmm... that's not really worse than the nixos.org/nix/install installer, right? | 20:54:02 | |
| no, I'm just speaking to my impression of the static build's maintenance state | 20:56:20 | |
| right, so i guess at least for now it's not a great thing to be shipping to users | 20:57:08 | |
the failures have not always been due to regressions in other packages IIRC, but it's been a while since I checked. just know my last nixpkgs-review failed to build it | 20:57:18 | |
In reply to @dramforever:matrix.orgGenerally it’s the dependencies that are broken in nixpkgs. Nix’s jobset from a release branch (e.g. 2.32-maintenance) is a well supported as the regular dynamically linked nix. | 21:58:59 | |
| Since nix’s nixpkgs flake input is from a stable release for the better part of the nixpkgs release cycle it tends to get fixed. | 21:59:52 | |
In reply to @dramforever:matrix.orgI don’t understand how you get that conclusion tho. It’s not nix that is poorly maintained, but the dependencies that spontaneously explode in nixpkgs. As always though it’s not a great idea to use the ‘master jobset for anything other than dogfooding. Using anything from*-maintenance` is perfectly fine and supported | 22:02:42 | |