| 28 Mar 2025 |
 3pleX-dev | In reply to @raboof:matrix.org
I don't know anything about Outreachy-specifics (is probably a question for Fernando Rodrigues) but I'd expect nixpkgs to be in scope :) Okay no worries, thank you. I’ve found the issues related to this project | 13:27:47 |
 Fernando Rodrigues | In reply to @3plexdev:matrix.org
Hello everyone,
I'm Emmanuel, an Outreachy participant interested in contributing to NixOS reproducible builds. I've gone through the contribution guidelines and have already made some initial contributions, which you can find here:
https://github.com/ngi-nix/ngipkgs/issues?q=is:pr+author:3pleX-dev
Now, I'm ready to start working on issues related to NixOS reproducible builds.
However, I’m a bit confused. I noticed that all projects on the Outreachy page have similar contribution guides, and the initial contribution instructions led me to ngi-nixpkgs. Since all the "good first issue" contributions are under that repository, I’m not sure if those contributions will count towards this project.
Could someone clarify this for me?
Thanks! Hi Emmanuel. It seems you have chosen the NGI project, which is different from the reproducible builds project. Please take a look at the reproducible builds project for specific instructions as to where to begin. | 13:35:20 |
| Fernando Rodrigues | In reply to @3plexdev:matrix.org
Hello everyone,
I'm Emmanuel, an Outreachy participant interested in contributing to NixOS reproducible builds. I've gone through the contribution guidelines and have already made some initial contributions, which you can find here:
https://github.com/ngi-nix/ngipkgs/issues?q=is:pr+author:3pleX-dev
Now, I'm ready to start working on issues related to NixOS reproducible builds.
However, I’m a bit confused. I noticed that all projects on the Outreachy page have similar contribution guides, and the initial contribution instructions led me to ngi-nixpkgs. Since all the "good first issue" contributions are under that repository, I’m not sure if those contributions will count towards this project.
Could someone clarify this for me?
Thanks! * | 13:35:33 |
| 3pleX-dev | Yes I have seen this now, the docs in the outreachy site had me confused for a bit, I was initially trying to follow through step-by-step. The ngipkgs repo was also referenced for good first contributions under reproducible build section
thank you so much for clarifying this Fernando Rodrigues | 14:04:45 |
| 30 Mar 2025 |
|  @dillyp3131:matrix.org joined the room. | 15:35:55 |
| 31 Mar 2025 |
|  @loving-melody:matrix.org joined the room. | 17:29:10 |
 Pol | How do you deal with packages that are not reproducible on mac? Context: https://github.com/NixOS/nixpkgs/pull/394620 | 19:35:30 |
| Pol | Redacted or Malformed Event | 19:37:01 |
| 1 Apr 2025 |
| 3pleX-dev | Hi Pol thank you for the feedback, I’ll look into this | 07:14:38 |
| Pol | Cool, let me know if I can help | 07:14:53 |
|  Sandro 🐧 changed their display name from Sandro 🐧 to "Sandro [c3d2]". | 13:56:49 |
| Sandro 🐧 changed their display name from "Sandro [c3d2]" to Sandro 🐧 [c3d2]. | 13:57:31 |
| Sandro 🐧 changed their display name from Sandro 🐧 [c3d2] to Sandro 🐧. | 13:59:03 |
|  Adam Neverwas set a profile picture. | 23:15:40 |
| 2 Apr 2025 |
 raboof | any additional eyes on figuring out what's going on with jemalloc in https://github.com/NixOS/nixpkgs/pull/393724 would be welcome - this is the last remaining known issue for the minimal iso and needs to go through staging... | 08:18:42 |
| Pol | The diff LGTM and make sense. Building stuff straight from the repository, not using artifacts (remind me somethinxz! ) | 08:24:11 |
| raboof | notably someone with C experience who can judge whether it'd be safer to over-estimate or under-estimate the LG_VADDR value in https://github.com/jemalloc/jemalloc/blob/dev/include/jemalloc/internal/rtree.h would be a great help :) | 09:51:45 |
| Pol | Packaging this library is a nightmare... I thought that Apache Foundation would be more sensible to reproducibility... but nope. https://github.com/apache/orc
The build process download stuff from Internet, it seems very hard to get around it. | 14:37:01 |
| Pol | Got it building in the end. | 16:35:37 |
|  rntpts joined the room. | 19:13:16 |
| 3 Apr 2025 |
|  diamond (it/its) changed their display name from Diamond (it/she) to diamond (it/its). | 01:07:09 |
 emily | raboof: I think you broke jemalloc:
#define JEMALLOC_VERSION "0.0.0-0-g000000missing_version_try_git_fetch_tags"
#define JEMALLOC_VERSION_MAJOR 0
#define JEMALLOC_VERSION_MINOR 0
#define JEMALLOC_VERSION_BUGFIX 0
#define JEMALLOC_VERSION_NREV 0
#define JEMALLOC_VERSION_GID "000000missin"
#define JEMALLOC_VERSION_GID_IDENT 000000missin
| 02:13:16 |
| Fernando Rodrigues | reproducibly broken is still reproducible :) | 02:13:47 |
| Pol | That's the spirit :D | 07:24:20 |
| raboof | 'the most secure code is code that doesn't run'? 🦆 | 07:41:13 |
| raboof | (fixing) | 07:41:15 |
| 5 Apr 2025 |
|  guider-le-recit joined the room. | 12:03:56 |
|  @tinybronca:sibnsk.net removed their display name underpantsgnome. | 15:52:40 |
| @tinybronca:sibnsk.net left the room. | 15:53:18 |
| 6 Apr 2025 |
| guider-le-recit | Hello everyone, my name is Keanu an outreachy intern hoping to work on nix if its not too late. I've gone through the nixdev documentation and pkgs reference manual, and started looking into the reproducibility issue for libpinyin #393693.
After tracing the code trough the DB files, i thought the problem was in memorychunk, it looks to properly handle its own memory initialization. My question is the non determinism coming from potentially uninitialized padding within the c++ structs, or is there something else to account for?
im thankful for any direction | 01:12:36 |
