| 13 Jan 2025 |
|  goibhniu changed their display name from goibhniu-test to goibhniu. | 19:17:25 |
 adarcy | Hi guys, one dependency of a package (flax) takes up all my RAM for testing and makes my computer freeze. | 20:26:38 |
 Perchun Pak | is there a reason to default go's ldflags to -w -s?
https://github.com/nix-community/nix-init/commit/78c29f5a81f4d5003f0b510a7fe1339c0f71ec23 | 20:26:56 |
| adarcy | I've tried systemd-run --user --scope -pMemoryMax=8G -pMemorySwapMax=50G nix-build ... but it does not work :( Any fix ? | 20:27:05 |
| Perchun Pak | you can create 100gb swap file or pass -j 1 & --cores 1
-j controls parallel builds, --cores controls amount of CPU cores used by one job (-j 3 --cores 4 will use 12 cores in total) | 20:28:45 |
| adarcy | Perchun Pak: that did it ! thanks :) | 20:32:24 |
 Niklas Korz | In reply to @perchun:matrix.org
is there a reason to default go's ldflags to -w -s?
https://github.com/nix-community/nix-init/commit/78c29f5a81f4d5003f0b510a7fe1339c0f71ec23 Those remove the debug symbols. In a nix package you either want no debug symbols or move them to a separate debug output. | 20:33:00 |
 matthewcroughan | Is libressl failing for anyone ? | 20:52:51 |
| matthewcroughan | 48/58 Test #54: tlstest ..........................***Failed 0.04 sec
tlstest: client handshake failed: certificate verification failed: certificate has expired
== TLS tests ==
| 20:52:57 |
| matthewcroughan | might be rare | 20:53:28 |
| matthewcroughan | nah seems to be reproducible | 20:53:36 |
| matthewcroughan | some old nixos container closure I think | 20:54:48 |
| matthewcroughan | goes to show why containers don't work really, imo | 20:55:11 |
| matthewcroughan | just encourages you to not move forward with things | 20:55:21 |
| matthewcroughan | * just encourages you to not move forward with things, then this happens, too easy to pin | 20:55:31 |
| matthewcroughan | This is me trying to rnu a nixos 22.05 container on the current nixos-unstable | 20:57:52 |
| matthewcroughan | * This is me trying to run a nixos 22.05 container on the current nixos-unstable | 20:57:58 |
| matthewcroughan | On the other hand it also suggests that certs shouldn't be part of builds, or if they are, allowed to be impure to increase reproducibility. | 20:58:51 |
| adarcy | On a PR, 3 checks are in the queue for 2-3 days for aarch64 and darwin. Is that a known issue ? | 23:06:34 |
 adamcstephens | As far as I know we only have builders for x86_64-linux, so those other systems will never complete | 23:22:30 |
 hexa | #ofborg:nixos.org | 23:25:16 |
| 14 Jan 2025 |
| hexa | git operations major outtage | 00:12:07 |
| hexa | again | 00:12:08 |
| Perchun Pak | In reply to @matthewcroughan:defenestrate.it
This is me trying to run a nixos 22.05 container on the current nixos-unstable You could try manually backporting new certs to 22.05 | 04:43:12 |
| Perchun Pak | why is there both nixos/doc/manual/release-notes/rl-2505.section.md and doc/release-notes/rl-2505.section.md? | 06:59:54 |
| Perchun Pak | nevermind, found https://github.com/NixOS/nixpkgs/pull/371930 | 07:01:29 |
 Picnoir | Could somebody have a look at https://github.com/NixOS/nixpkgs/pull/372324 ? | 10:26:00 |
| Picnoir | * Could somebody have a look at/review https://github.com/NixOS/nixpkgs/pull/372324 ? | 10:26:10 |
| Perchun Pak | try https://discourse.nixos.org/t/prs-ready-for-review-december/1711 | 10:33:17 |
 hellwolf | https://github.com/NixOS/nixpkgs/pull/373563#discussion_r1914593287
I am not maintaining nixpkgs daily, could anyone help to explain this message to me? What made the "with" pattern undesirable and for when. | 10:40:47 |
