| 21 Dec 2024 |
 K900 | I think I brought this up before, but should we enable build-ids for everything | 07:36:51 |
 p14 | In reply to @k900:0upti.me
I think I brought this up before, but should we enable build-ids for everything Rationale? What are build-ids a function of and does it affect reproducible builds? (Presumably they don't, but would love to understand more what's going on and what they enable). | 11:03:43 |
| K900 | build-ids are basically a hash of the file | 11:11:21 |
| K900 | They're used for debug info matching | 11:11:28 |
| p14 | I see. Is there a pool of debug info somewhere I can easily utilise? | 11:12:08 |
| K900 | We don't build debug info for everything | 11:12:44 |
| K900 | But many things have it cached | 11:12:48 |
| K900 | You can use nixseparatedebuginfod | 11:12:52 |
| p14 | That's pretty cool; I'm wondering how does it connect thing being debugged to the derivation containing the separate debug info. Thinking aloud, presumably it does something like nix-store --query --deriver <path> and then look inside the derivation for the output named 'debug'. | 11:16:29 |
|  Dimitar joined the room. | 19:45:27 |
 Philip Taron (UTC-8) | I'd like to post this | 21:45:12 |
 Tristan Ross | In reply to @philiptaron:matrix.org
I'd like to post this On Discourse? | 21:47:20 |
| Philip Taron (UTC-8) | Yessir. | 21:47:27 |
