 | Staging | 394 Members |
| Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen | 127 Servers |
| Staging | 394 Members |
| Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen | 127 Servers |
| Sender | Message | Time |
|---|---|---|
| 25 Jun 2026 | ||
 K900 | And once that is done we'll still need it to chew through the merge | 09:51:38 |
 emily | I heard chewing through merge only takes hours now? (n=1 I guess) | 09:52:02 |
 hexa | which does seem to happen fairly fast | 09:52:03 |
| hexa |  Download Gaétan Lepage torchaudio is not healthy on hydra, tends to run into dependenncy issues or timeouts | 10:02:20 |
| hexa | it also uses lots of openmp threads from what I can tell, please reduce those | 10:03:05 |
 Vladimír Čunát | Yes, I think I'll merge staging-next within several hours. | 12:52:25 |
 whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get is | 18:01:37 |
| whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get for nix-build -A stdenvNoCC is | 18:01:55 |
| whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get for nix-build -A stdenvNoCC is | 18:03:02 |
 Gaétan Lepage | Ok, thanks for the ping. I'll have a look. I know tests are quite hungry. | 18:03:53 |
| whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get for nix-build -A stdenvNoCC --system aarch64-linux is | 18:06:06 |
| whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get for nix-build -A stdenvNoCC --system aarch64-linux isedit: bisecting was shorter than i thought. looks like it was broken by https://github.com/NixOS/nixpkgs/pull/532074, since it works on 75e94d8 and fails on eb7592e | 18:10:26 |
| whispers [& it/fae] | hm. i don't know where to ask about this/search for information (especially since it might be my fault, computers have been acting up), it may or may not be known already, but is stdenvNoCC broken on staging for aarch64-linux? am on commit 03357d87710d8b303d13d8889ff7a7a428e338ea. error i get for nix-build -A stdenvNoCC --system aarch64-linux isedit: bisecting was shorter than i thought. looks like it was broken by https://github.com/NixOS/nixpkgs/pull/532074, since it works on 75e94d8 and fails on eb7592e. i can't tell why it's happening though… | 18:11:13 |
 Grimmauld (any/all) | can confirm, and not an issue on x86_64-linux | 18:12:19 |
| Vladimír Čunát | staging-next merged! | 19:03:57 |
| Gaétan Lepage | That was the small one, best on 26.05's staging, right? | 20:12:19 |
| Gaétan Lepage | * That was the small one, based on 26.05's staging, right? | 20:12:32 |
| hexa | yes | 20:17:21 |
| 26 Jun 2026 | ||
| emily | working on this now | 03:43:22 |
| emily | plan still for 26.11 imminently? | 03:43:31 |
| Vladimír Čunát | I guess so. I'm not aware of any relevant news. | 04:21:09 |
| Grimmauld (any/all) | In reply to @vcunat:matrix.orgMay want to look into why stdenvNoCC fails on aarch64-linux on staging branch before starting | 05:48:24 |
| Grimmauld (any/all) | Or well, we know why (GCC 15.3.0) but I don't think we have a fix | 05:49:03 |
| Vladimír Čunát | You know which particular change inside 15.2 -> 15.3? | 05:52:19 |
| Grimmauld (any/all) | In reply to @whispers:catgirl.cloudOnly repeating what whispers found out. I didn't do the bisect, I just confirmed the failure | 05:54:31 |
| Vladimír Čunát | One option is to just revert the gcc bump for now, until this is fixed 🤷 | 05:58:30 |
| Vladimír Čunát | That's what I plan to do when starting staging-next. | 05:59:13 |
| emily | https://github.com/NixOS/nixpkgs/pull/535508 should cover everything that has enough rebuilds to want to land before staging starts; I'll build stdenv on that now (cc Randy Eckenrode too). https://github.com/NixOS/nixpkgs/pull/535513 fixes a regression caused by the drop. cleaning up my big branch of fixing packages that will have their update scripts break from the drop, but that shouldn't cause many rebuilds | 07:05:59 |
 Myria | I have a fix for the aarch64-darwin stuff with GCC 15.3.0, not sure about the linux stuff? | 07:17:06 |
| Grimmauld (any/all) | if you have a PR i can poke a build on aarch64-linux and see if stdenvNoCC happens to be fixed by it "accidentally" (worth a shot, even if unlikely) | 07:20:51 |