24 Oct 2024 |
emily | I guess this got an entire merge squashed into a single commit? | 10:25:18 |
Atemu |
If you make something idiot-proof, someone will just make a better idiot.
| 10:39:32 |
Atemu | (No offense) | 10:39:36 |
Alyssa Ross | In reply to @emilazy:matrix.org Alyssa Ross: sorry to ping but feedback on https://github.com/NixOS/nixpkgs/pull/349555#issuecomment-2426754636 would be helpful as I'm worried about Rust bindgen regressing on Darwin for the whole 24.11 release cycle ack | 10:43:10 |
Alyssa Ross | oh right that thing | 10:43:30 |
Alyssa Ross | yes, I trust you to do the right thing here | 10:44:14 |
Alyssa Ross | Tethys SvenssonI got sick, so I haven't had a chance to look at binutils yet. I will try to after NixCon (or possibly during if I'm not well enough to go…)
| 10:45:23 |
emily | thanks :) my hope is that we can figure out a way to avoid this entirely on all platforms at some point – e.g. not having a default sysroot of / if we don't actually want system libraries to be picked up with unwrapped compilers on non-NixOS Linux (though I understand there are other things to figure out to make that work okay) | 10:45:27 |
emily | hope you feel better soon | 10:45:41 |
Alyssa Ross | (I have a hope that normalizing ack comments on PRs will result in less stuck PRs waiting for somebody to look at them. "I haven't reviewed but don't feel I need to" is such a useful thing to be able to express quickly.) | 10:48:56 |
emily | would be nice to have a button for it… | 10:49:21 |
emily | although if it took as many clicks to press as the checkmark currently does it might not be any faster :') | 10:49:37 |
Alyssa Ross | hehe | 10:51:25 |
Alyssa Ross | yeah this is something the GitHub workflow really lacks | 10:51:30 |
Alyssa Ross | and is extremely normal elsewhere | 10:51:39 |
netthier | How long does it usually take for a backported PR to land in the nixos-24.05 channel :think | 11:44:39 |
netthier | * How long does it usually take for a backported PR to land in the nixos-24.05 channel 🤔 | 11:44:45 |
netthier | Specifically interested in this PR https://github.com/NixOS/nixpkgs/pull/350639 | 11:44:52 |
K900 | https://nixpk.gs/pr-tracker.html?pr=350639 | 11:45:10 |
Alyssa Ross | a day or two usually | 11:45:26 |
netthier | I've seen that, but I'm not sure how to determine when it will hit said channel based on that | 11:45:28 |
netthier | In reply to@qyliss:fairydust.space a day or two usually Thanks 👍️ | 11:46:17 |
JCaesar | In reply to @netthier:matrix.org I've seen that, but I'm not sure how to determine when it will hit said channel based on that Yeah, it's not really for "when it will", it's for "when it has". | 12:11:18 |
JCaesar | * Yeah, it's not really for "when it will", it's for "if it has". | 12:13:54 |
emily | forgive me for this awful question, but – is there a way to detect whether a package argument has been overridden or is direct from callPackage ? | 12:48:22 |
emily | as in, a version of callPackage ({ packageThatExists ? null }: …) that works? | 12:48:34 |
aleksana (force me to bed after 18:00 UTC) | In reply to @aleksana:mozilla.org
Is there something new with nss cacert? Now running nixpkgs-review with every PRs fail with error checking the existence of https://tarballs.nixos.org//sha256-5v54irD0Celu78tbx5zp60KF4Xv5HyUjhz/BY+M+vi4=:
curl: (77) error setting certificate file: /nix/store/h8qhspg7pml84z8s4ghrhmx6m77rs161-nss-cacert-3.104/etc/ssl/certs/ca-bundle.crt
While running nix-build foo.src --check on latest Nixpkgs checkout with multiple packages is fine Still can't understand where's the problem... Checking out locally or merging to latest master is still fine | 15:11:55 |
| zi3m5f joined the room. | 16:07:05 |
ghpzin | In reply to@emilazy:matrix.org as in, a version of callPackage ({ packageThatExists ? null }: …) that works? If you use pkgs there, you can maybe check if it is equal to what you expected to be there by default. | 16:25:13 |
ghpzin | If you can use pkgs there, you can maybe check if it is equal to what you expected to be there by default. | 16:25:22 |