| 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 (@38c3 📞488{0,1}) changed their display name from elikoga to elikoga (@38c3 📞448{0,1}. | 15:21:37 |
| elikoga (@38c3 📞488{0,1}) changed their display name from elikoga (@38c3 📞448{0,1} to elikoga (@38c3 📞448{0,1}). | 15:25:56 |
| elikoga (@38c3 📞488{0,1}) changed their display name from elikoga (@38c3 📞448{0,1}) to elikoga (@38c3 📞488{0,1}). | 15:26:35 |
|  phaer (8650 at 38c3) changed their display name from phaer to phaer (8650 at 38c3). | 17:42:35 |
| 27 Dec 2024 |
|  raitobezarius (DECT: 3538 / EPVPN 2681) 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 |
| emily | if they're reproducible build fanatics yeah. if they're just maintainers of the package perhaps not? | 21:33:09 |
| SigmaSquadron | Ah! So the reports are meant for the maintainers, not the people in here. That makes more sense.
I'll just put everything in a textarea then.
| 21:34:04 |
| 28 Dec 2024 |
 Pol | FWIW, the issue template is linked from this page too: https://reproducible-builds.org/contribute/nixos/ | 08:42:13 |
| Pol |
Use the issue template on GitHub to report your issues and hopefully, your solution.
| 08:42:20 |
| SigmaSquadron | That link will need to be updated to point to 11 unreproducible_package.yml (or 10 unreproducible_package.yml, depends on whether or not we remove the tracking template) | 08:52:07 |
| SigmaSquadron | But otherwise nothing should change. | 08:52:25 |
| 19 May 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 16:14:09 |
|  Alyssa Ross joined the room. | 16:14:59 |
|  baloo joined the room. | 16:15:12 |
| baloo | 16:15:29 |
