| 26 Dec 2024 |
| 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 |
Fernando Rodrigues | 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 |
Fernando Rodrigues | * 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 |
Fernando Rodrigues | 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 |
Fernando Rodrigues | 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 |
Fernando Rodrigues | 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 |
Fernando Rodrigues | But otherwise nothing should change. | 08:52:25 |
| 29 Dec 2024 |
| elikoga changed their display name from elikoga (@38c3 📞488{0,1}) to elikoga (@38c3 📞488{0,1,9}). | 11:02:51 |
| 30 Dec 2024 |
| raitobezarius changed their display name from raitobezarius (DECT: 3538 / EPVPN 2681) to raitobezarius. | 16:29:54 |
| 31 Dec 2024 |
| siraben left the room. | 14:51:20 |
| phaer changed their display name from phaer (8650 at 38c3) to phaer. | 19:24:26 |
| 1 Jan 2025 |
| oliver.falvai joined the room. | 10:45:28 |
| mjolnirchanged room power levels. | 14:26:26 |
| jopejoe1 (4094@39c3) changed their display name from jopejoe1 [4094] to jopejoe1. | 23:30:14 |
| 3 Jan 2025 |
| elikoga changed their display name from elikoga (@38c3 📞488{0,1,9}) to elikoga. | 10:28:01 |
| 4 Jan 2025 |
| @kranzes:matrix.org left the room. | 15:31:06 |
| 6 Jan 2025 |
emily | "You can try the new experimental -fobject-determinism flag to enable deterministic object code generation." https://blog.haskell.org/ghc-9-12-cabal-3-14/ 👀 | 23:24:56 |
| 7 Jan 2025 |
Pol | https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/1179e9457bf7280f1954a33b6505cc6bdff33442 | 07:47:41 |
Pol | Thanks for the heads up | 07:47:50 |
| Fernando Rodrigues changed their display name from SigmaSquadron to SigmaSquadron (Away until 2024-01-12). | 19:35:57 |
| 9 Jan 2025 |
Pol | It is published: https://reproducible-builds.org/reports/2024-12/#other-development-news | 12:13:55 |
| 10 Jan 2025 |
| Fernando Rodrigues changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11). | 22:15:46 |
| Fernando Rodrigues changed their display name from SigmaSquadron (Away until 2024-01-11) to SigmaSquadron (Away until 2025-01-11). | 22:43:19 |
| 11 Jan 2025 |
| @orzklv:matrix.org left the room. | 04:07:35 |