| 5 Oct 2025 |
 dish [Fox/It/She] | * but also it does make sense >.> | 00:05:49 |
| dish [Fox/It/She] | Okay, confirmed that the new bootstrap chain fully builds. I'm going to push my changes as they stand right now as a PR, and start a new branch rebasing emily's changes from #260193 to my branch. | 00:51:19 |
| dish [Fox/It/She] | https://github.com/nixos/nixpkgs/pull/448701 | 00:57:10 |
| dish [Fox/It/She] | Okay, confirmed that the updated bootstrap chain fully builds. I'm going to push my changes as they stand right now as a PR, and start a new branch rebasing emily's changes from #260193 to my branch. | 01:06:48 |
 Lun | gz on getting that to this point! | 01:07:31 |
| dish [Fox/It/She] | thank you! | 01:10:58 |
 dramforever | Lun: do you happen to know whom i should cc for those darwin bootstrap tools shenanigans | 01:13:15 |
| dramforever | like i fixed ... something, but as i've written it's going to be a problem next time someone goes to roll the bootstrap tarballs | 01:13:45 |
| Lun | reckenrode? | 01:13:55 |
| dish [Fox/It/She] | also I've just realized that my current strategy of picking individual commits(in sequence one at a time) from emily's branch is going to involve a lot of rebuilding the same stuff over and over(for instance pulling the static coreutils commit rebuilt everything up to musl 1.1, and then picking the static gnutar commit is doing that same build process again, which means I'm gonna be building several dozen GCCs by the end of this) , but I would rather do that then break something and not know where to start. Also this means that it something breaks i know where and when which will help me a lot. | 01:14:45 |
| dish [Fox/It/She] | * also I've just realized that my current strategy of picking individual commits(in sequence one at a time) from emily's branch is going to involve a lot of rebuilding the same stuff over and over(for instance pulling the static coreutils commit rebuilt everything up to musl 1.1, and then picking the static gnutar commit is doing that same build process again, which means I'm gonna be building several dozen GCCs by the end of this) , but I would rather do that then break something and not know where to start. This means that it something breaks i know where and when which will help me a lot. | 01:14:55 |
| dish [Fox/It/She] | * also I've just realized that my current strategy of picking individual commits(in sequence one at a time) from emily's branch is going to involve a lot of rebuilding the same stuff over and over(for instance pulling the static coreutils commit rebuilt everything up to musl 1.1, and then picking the static gnutar commit is doing that same build process again, which means I'm gonna be building several dozen GCCs by the end of this) , but I would rather do that then break something and not know where to start. This means that it something breaks i know where and when which will help me a lot while i cherry-pick these | 01:15:02 |
| dish [Fox/It/She] | each rebuild is like 20 minutes though so it's slow going | 01:15:10 |
| dish [Fox/It/She] | * each rebuild is like 20 minutes though so it's slow going, however its only like 20 commits and once I'm done then i can keep going more smoothly | 01:15:23 |
| dish [Fox/It/She] | * also I've just realized that my current strategy of picking individual commits(in sequence one at a time) from emily's branch is going to involve a lot of rebuilding the same stuff over and over(for instance pulling the static coreutils commit rebuilt everything up to musl 1.1, and then picking the static gnutar commit is doing that same build process again, which means I'm gonna be building several dozen GCCs(4.6.4 -> 4.6.4 with c++ -> 8.5.0 -> 13.2.0 before getting to static binaries, potentially every time) by the end of this) , but I would rather do that then break something and not know where to start. This means that it something breaks i know where and when which will help me a lot while i cherry-pick these | 01:16:53 |
| dramforever | is this like, automated | 01:17:02 |
| dramforever | i've done stuff like this just going git rebase -x 'do the thing' and went to get lunch or something, 20 minutes per commit is, a bit slow but not the worst | 01:18:06 |
| dish [Fox/It/She] | no, there's merge conflicts every commit | 01:19:05 |
| dish [Fox/It/She] | so i have to do it manually | 01:19:08 |
| dish [Fox/It/She] | but as a free time project i don't mind | 01:19:21 |
| dish [Fox/It/She] | * but as a free time project i don't mind doing these rebuilds slowly | 01:19:29 |
| dramforever | oh, yeah, if there's a lot to tweak then doing it manually makes sense | 01:20:18 |
| dramforever | thanks, they're in the requested review list but i've pinged to more explicitly say that bootstrap will need fixing | 01:26:57 |
| Lun | dish [Fox/It/She]: i wanna try to rescue the original version of the musl flush patch so it just flushes before exit instead of turning off buffering, is it ok if i pr against your pr's branch if i get it working? | 01:42:44 |
| dish [Fox/It/She] | PRing against my branch would be fine, I'm also fine just cherry-picking it across if you make your own branch. Whichever works best for you!@ | 01:47:07 |
| dish [Fox/It/She] | * PRing against my branch would be fine, I'm also fine just cherry-picking it across if you make your own branch. Whichever works best for you! | 01:47:08 |
| dish [Fox/It/She] | okay its going much quicker now that its basically new "leaf" packages lol | 01:57:18 |
| dish [Fox/It/She] | not modifying older ones like getting new static builds of old binaries or anything | 01:57:34 |
| dish [Fox/It/She] | okay that took a lot less time than I thought. I've applied all of emily's commits, fixed them up(a few package updates, reformatting everything, and ensuring each successive step builds), and am now building the final bash-static derivation from emily's branch. Next steps are detailed in her PR description | 02:52:21 |
| Lun | https://github.com/NixOS/nixpkgs/commit/67eec45505b79dd38d7abf4d18ec037bcc3ea940 | 02:58:42 |
