| 24 Apr 2026 |
 Vladimír Čunát | nixpkgs-unstable updated 🎉 It had almost 8 days of lag at that point, sadly, partially because of getting multiple blockers. | 05:47:49 |
 matthewcroughan | What is the etiquette of merging things that cause large amounts of rebuilds into staging? | 14:09:30 |
| matthewcroughan | I want to merge https://github.com/NixOS/nixpkgs/pull/511517 but don't know if it'll cause people to yell at me for doing the wrong thing | 14:10:14 |
 leona | merging large rebuilds to staging is the intended thing. It would be good if you could test a few dependent bulids if they could fail. Otherwise you can likely just merge | 14:11:45 |
| matthewcroughan | I believe it to be the right fix, yeah, and I have tested it on a pi zero, so full deps really | 14:12:09 |
| matthewcroughan | i.e a toplevel containing it as a closure | 14:12:17 |
| matthewcroughan | * i.e a toplevel containing it in the closure | 14:12:38 |
| matthewcroughan | An app that depends on it was failing due to it, so that's how I tested it | 14:12:51 |
| leona | imo fine to merge it then. (ideally a maintainer approves as always) | 14:13:06 |
| matthewcroughan | It's kind of been sitting there for a bit, I wanted to speed it up, I can almost guarantee that if I do nothing it'll still be there in a week, and nobody will review it. | 14:13:51 |
| matthewcroughan | Which would be fine if it weren't such a trivial change | 14:15:05 |
 Alyssa Ross | I think I need to start being less indirect when I'm writing commetns on your PRs :)
In this case, what I meant is "if you confirm that your best guess is that upstream would probably consider it sensible to list this in their pyproject.toml dependencies, I would merge the PR if it were changed to do that" | 14:16:36 |
| matthewcroughan | Rather my understanding is that this mistake of putting pybind11 in nativeBuildInputs seems to be common throughout nixpkgs | 14:17:16 |
| Alyssa Ross | I wonder why that specifically | 14:17:52 |
| matthewcroughan | and that this is one example of a trivial fix, but I didn't understand what build-system mapped to until you commented | 14:17:56 |
| matthewcroughan | There's another package I can test this on actually | 14:19:36 |
| matthewcroughan | laszip | 14:20:00 |
| matthewcroughan | In that case, pybind11 is in build-system but cross works | 14:20:12 |
| matthewcroughan | Oh, that doesn't seem to contain pybind, is my grep fscked up | 14:21:40 |
| matthewcroughan | Uh no there is pkgs/by-name/la/laszip and pkgs/development/python-modules/laszip | 14:22:28 |
| matthewcroughan | is it considered an issue when there is a by-name package that name clashes with something in a package set? | 14:22:42 |
| matthewcroughan | So ignore what I said.. let me try that again.. | 14:23:01 |
| 28 Jun 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 15:07:04 |
| @grahamc:nixos.org changed the room name to "" from "". | 15:07:04 |
| @grahamc:nixos.org changed the room topic to "" from "". | 15:07:04 |
| @grahamc:nixos.org invited  mjolnir. | 15:07:15 |
| @grahamc:nixos.org invited  hexa. | 15:07:16 |
| mjolnir joined the room. | 15:07:16 |
| @grahamc:nixos.orgchanged room power levels. | 15:07:20 |
| hexa joined the room. | 15:07:20 |
