| 19 Jul 2021 |
 Reventlov | Redacted or Malformed Event | 11:40:22 |
 andi- | What drives our tinycc compilation if all you have is an assembler? If you want to bootstrap the Nixpkgs stdenv you need to somehow provide a shell as part of the bootstrap process. | 11:41:35 |
| andi- | You could also impurely use the hosts /bin/sh that is always there during a build... | 11:42:15 |
|  j-k joined the room. | 15:01:05 |
 siraben | minimal bootstrap issue https://github.com/NixOS/nixpkgs/issues/123095 | 16:52:56 |
| siraben | Like Guix we have a great opportunity to just reduce the bootstrap without affecting anything else (modulo some rebuilds) | 16:53:49 |
 tomberek | andi-: I presume one can hand-assemble an execvpe call directly if needed. Would be smaller than bringing in a shell. But one has to assume a few resident things anyway, a POSIX shell isn’t onerous as an assumption, and a filesystem, and host OS. From a different angle; another fun bootstrapping exercise: https://niedzejkob.p4.team/bootstrap/miniforth/ | 22:40:54 |
| 20 Jul 2021 |
|  ldesgoui joined the room. | 14:36:47 |
|  sumner left the room. | 21:42:46 |
| 25 Jul 2021 |
| tomberek | Updated the gnome build report: https://tomberek.info/r13y.com/
grahamc (he/him) I'm not sure people are aware of https://r13y.com/trivial/index.html , https://r13y.com/iso_minimal/index.html and https://r13y.com/iso_gnome/index.html . Their textual content is wrong, but I'm working on PRs to fix that. | 20:42:12 |
 @grahamc:nixos.org | Great! | 20:43:36 |
| @grahamc:nixos.org | I think it will not be so hard to make it actually succeed in building, too :). | 20:44:11 |
| tomberek | I have a fairly weak machine doing the gnome build; takes 4 days, but it eventually succeeds. | 21:01:15 |
| 26 Jul 2021 |
 Gytis Ivaskevicius | In reply to @tomberek:matrix.org
I have a fairly weak machine doing the gnome build; takes 4 days, but it eventually succeeds. dam, thats alot of days. Lack of ram or something? May I know for reference what hardware is it running? | 03:01:18 |
| tomberek |
dam, thats alot of days. Lack of ram or something? May I know for reference what hardware is it running?
Dell PowerEdge with dual Intel Xeon 5160 with 16GiB ECC RAM. It's an old server running in my basement.
| 13:50:06 |
| 27 Jul 2021 |
| siraben | does anyone want to look at https://github.com/NixOS/nixpkgs/pull/85542 ? (full source bootstrap of Rust) | 11:49:36 |
| 28 Jul 2021 |
|  prusnak changed their display name from prusnak to stick. | 15:09:43 |
| 29 Jul 2021 |
|  srid changed their display name from srid (on hiatus) to srid. | 01:28:38 |
| prusnak changed their display name from stick to stick2. | 16:25:23 |
| prusnak changed their display name from stick2 to stick. | 16:25:57 |
|  Artturin joined the room. | 17:27:20 |
| 30 Jul 2021 |
 raboof | https://github.com/NixOS/nixpkgs/pull/120858 was just merged which should enable building the unoptimized python bytecode again, which is great for performance but likely brings back an unreproducibility. | 09:06:14 |
| raboof | the good news is we have a clear suspect for where that unreproducibility might come from, https://github.com/NixOS/nixpkgs/issues/132037 - no patch yet though :) | 09:06:43 |
| prusnak changed their display name from stick to stick3. | 10:32:55 |
| prusnak changed their display name from stick3 to stick. | 10:33:03 |
| prusnak changed their display name from stick to stick[m]. | 10:35:18 |
| prusnak changed their display name from stick[m] to stick. | 10:35:44 |
| tomberek | It seems that the pyc fix would be for python 3.9 and not backported. If so, does that mean we just wait? | 18:42:27 |
| andi- | Next release can then carry these changes. Why would be backport it? | 18:49:45 |
| raboof | it looks like on unstable 'python3' already points to 'python39', so if the fix would land in 3.9 that'd be OK by me. but if someone has the energy to backport it, why not :) | 18:54:37 |
