| 4 Dec 2024 |
 @statecode47:unredacted.org | In reply to @raboof:matrix.org
Nice! And the rest was bit-by-bit identical with upstream? That's pleasantly surprising! * | 22:14:24 |
| 5 Dec 2024 |
| @statecode47:unredacted.org removed their profile picture. | 19:06:41 |
| @statecode47:unredacted.org removed their display name statecode47. | 19:06:41 |
| @statecode47:unredacted.org left the room. | 19:06:43 |
| 8 Dec 2024 |
|  shawn8901 set a profile picture. | 19:21:15 |
|  @freedom-foundation:matrix.org joined the room. | 19:53:06 |
|  mjolnir banned @freedom-foundation:matrix.org (persistently off topic). | 19:53:07 |
| 11 Dec 2024 |
|  @dminca:matrix.org left the room. | 14:18:57 |
|  marijan changed their profile picture. | 14:20:36 |
|  stick left the room. | 18:36:28 |
| 15 Dec 2024 |
|  Mel changed their profile picture. | 21:39:03 |
|  Raj joined the room. | 21:57:29 |
| 16 Dec 2024 |
|  @ksonj:matrix.org left the room. | 14:59:31 |
| 18 Dec 2024 |
|  @steeringwheelrules:tchncs.de left the room. | 13:54:07 |
|  @dmiskovic:matrix.org joined the room. | 19:37:44 |
| 21 Dec 2024 |
|  @stablejoy:matrix.org left the room. | 05:08:23 |
| @dmiskovic:matrix.org left the room. | 05:13:57 |
| @stablejoy:matrix.org joined the room. | 06:43:01 |
| 22 Dec 2024 |
| @stablejoy:matrix.org left the room. | 13:25:07 |
|  allrealmsoflife joined the room. | 15:55:05 |
| 25 Dec 2024 |
|  CJ joined the room. | 14:39:52 |
| 26 Dec 2024 |
|  elikoga changed their display name from elikoga to elikoga (@38c3 📞448{0,1}. | 15:21:37 |
| elikoga changed their display name from elikoga (@38c3 📞448{0,1} to elikoga (@38c3 📞448{0,1}). | 15:25:56 |
| elikoga changed their display name from elikoga (@38c3 📞448{0,1}) to elikoga (@38c3 📞488{0,1}). | 15:26:35 |
|  phaer changed their display name from phaer to phaer (8650 at 38c3). | 17:42:35 |
| 27 Dec 2024 |
|  raitobezarius changed their display name from raitobezarius to raitobezarius (DECT: 3538 / EPVPN 2681). | 07:33:22 |
 SigmaSquadron | Hi friends. I'm working on converting the Nixpkgs issue templates to YAML forms, and the in reproducible package is the last one to go. Thing is, I'm unsure how to proceed; it's not your typical issue template, since it provides step-by-step instructions on how to rebuild the package. Issue forms would allow us to only show those lengthy instructions to the reporter, and the final issue would only include the relevant information. (Package name and version, Nixpkgs revision, diffoscope log and additional context.) So, are those instructions meant to be visible in the final issue? | 21:23:50 |
| SigmaSquadron | * Hi friends. I'm working on converting the Nixpkgs issue templates to YAML forms, and the unreproducible package template is the last one to go. Thing is, I'm unsure how to proceed; it's not your typical issue template, since it provides step-by-step instructions on how to rebuild the package. Issue forms would allow us to only show those lengthy instructions to the reporter, and the final issue would only include the relevant information. (Package name and version, Nixpkgs revision, diffoscope log and additional context.) So, are those instructions meant to be visible in the final issue? | 21:24:15 |
 emily | I think the reproduction instructions are for people investigating the issue? | 21:28:43 |
| SigmaSquadron | But, wouldn't the people investigating the issue already know all that? | 21:29:40 |
