| 1 Nov 2025 |
 Mic92 | *
- mounted the installer dmg
- extraced the tar from the self-extracting installer
- untar the coverity toolchain
- /private/tmp/codcov2/bin/cov-configure --clang
- /private/tmp/codcov2/bin/cov-build --dir cov-int ninja -C build
- creating a tar. The tar should look like this:
nix-util-env % tar -tvf ./cov-int.tgz
drwxr-xr-x joerg/staff 0 2025-10-31 13:36 cov-int/
-rw-r--r-- joerg/staff 191 2025-10-31 13:36 cov-int/security-da-log.txt
-rw-r--r-- joerg/staff 21 2025-10-31 13:36 cov-int/build-cwd.txt
-rw-r--r-- joerg/staff 398 2025-10-31 13:36 cov-int/security-da-timings.txt
drwxr-xr-x joerg/staff 0 2025-10-31 13:36 cov-int/output/
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 |
 lovesegfault | This inside a nix develop shell? | 15:23:22 |
| Mic92 | yes. | 15:23:33 |
| Mic92 | I did run meson configure before. | 15:23:40 |
| * lovesegfault nods | 15:24:51 |
| lovesegfault | let me try from Linux | 15:24:58 |
| lovesegfault | it's going! | 15:49:54 |
| lovesegfault | Last Build Status: In-queue. Your build is in the queue to be analyzed. There are 99 builds ahead of it. | 16:12:51 |
| lovesegfault | From past experience, it will take a long while :P | 16:13:11 |
 John Ericson | Sergei Zimmerman (xokdvium): do you think instead of doing <"....."> we can use custom string literals? | 19:33:01 |
| John Ericson | that seems a little bit less stressful on the templating :) | 19:33:16 |
| John Ericson | hmm, seems to be working! | 19:47:38 |
| John Ericson | ah it was because auto not auto & | 20:00:02 |
| John Ericson | OK got it! | 20:15:42 |
| John Ericson | and I found that deleting the destructor will make auto instead of auto & a compile failure, yay! | 20:16:03 |
 dramforever | 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 |
| dramforever | * 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 |
| dramforever | 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 |
 emily | it regularly fails to build on Hydra fwiw | 20:52:00 |
| dramforever | on nix hydra or nixpkgs hydra? | 20:52:23 |
| emily | latter, but if they differ I assume only due to former's Nixpkgs lagging behind | 20:53:09 |
| dramforever | hmm... that's not really worse than the nixos.org/nix/install installer, right? | 20:54:02 |
| emily | no, I'm just speaking to my impression of the static build's maintenance state | 20:56:20 |
| dramforever | right, so i guess at least for now it's not a great thing to be shipping to users | 20:57:08 |
| emily | 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 |
 Sergei Zimmerman (xokdvium) | In reply to @dramforever:matrix.org
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 Generally 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 |
| Sergei Zimmerman (xokdvium) | 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 |
| Sergei Zimmerman (xokdvium) | In reply to @dramforever:matrix.org
right, so i guess at least for now it's not a great thing to be shipping to users I 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 ‘masterjobset for anything other than dogfooding. Using anything from*-maintenance` is perfectly fine and supported | 22:02:42 |
| Sergei Zimmerman (xokdvium) | In reply to @dramforever:matrix.org
right, so i guess at least for now it's not a great thing to be shipping to users * I 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:59 |
| emily | it's definitely not just failing deps, e.g. https://hydra.nixos.org/job/nixpkgs/trunk/nixStatic.aarch64-darwin/all and https://hydra.nixos.org/job/nixpkgs/trunk/nixStatic.x86_64-linux/all both have direct failures that persisted for quite some time | 22:12:20 |
