| 28 Jul 2025 |
maralorn | I just checked out recent nixos-unstable and it seems to work. | 17:58:30 |
maralorn | * I just checked out recent nixos-unstable and it seems to work for me. | 17:58:44 |
| 29 Jul 2025 |
sterni (he/him) | maralorn: do you have time to give https://github.com/NixOS/nixpkgs/pull/429212 a look over or should I just merge it and start an evaluation | 11:46:13 |
sterni (he/him) | * maralorn: do you have time to give https://github.com/NixOS/nixpkgs/pull/429212 a look over or should I just merge it and start an evaluation? | 11:46:16 |
sterni (he/him) | or others with relevant experience of course :p | 11:57:57 |
maralorn | I can take a look later. | 12:29:00 |
sterni (he/him) | Pierre Thierry: Feel free to open an issue about it, including enough information to hopefully reproduce the issue you're seeing. | 17:12:26 |
| 30 Jul 2025 |
dana | I need somethings from the https://github.com/NixOS/nixpkgs/pull/424162, which is now merged into staging. However, when I try to use it locally the caches aren't populated just yet, so I end up recompiling GHC. The caches are a bit confusing since staging or haskell-updates rev that I need don't have the cache, but it's not clear to me when are these changes going to end up in staging-next or master (which do have the caches).
Slightly unrelated question: how do things get merged from staging to staging-next in general? Because the https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging says that there should be a manual PR. However, I don't see anything similar when I search for PRs from staging to staging-next: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+base%3Astaging-next+head%3Astaging+ | 12:17:46 |
dana | * I need somethings from the https://github.com/NixOS/nixpkgs/pull/424162, which is now merged into staging. However, when I try to use it locally the caches aren't populated just yet, so I end up recompiling GHC. The caches are a bit confusing since staging or haskell-updates rev that I need don't have the cache, but it's not clear to me when are these changes going to end up in staging-next or master (which do have the caches). When do these changes usually propagate to master? Or what ref/rev should I take to get the caches earlier?
Slightly unrelated question: how do things get merged from staging to staging-next in general? Because the https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging says that there should be a manual PR. However, I don't see anything similar when I search for PRs from staging to staging-next: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+base%3Astaging-next+head%3Astaging+ | 12:19:40 |
maralorn | In reply to @bkl:matrix.org I need somethings from the https://github.com/NixOS/nixpkgs/pull/424162, which is now merged into staging. However, when I try to use it locally the caches aren't populated just yet, so I end up recompiling GHC. The caches are a bit confusing since staging or haskell-updates rev that I need don't have the cache, but it's not clear to me when are these changes going to end up in staging-next or master (which do have the caches).
Slightly unrelated question: how do things get merged from staging to staging-next in general? Because the https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging says that there should be a manual PR. However, I don't see anything similar when I search for PRs from staging to staging-next: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+base%3Astaging-next+head%3Astaging+ haskell-updates also gets cached, but there was a bag change today so you probably want a commit from a few days ago. | 12:22:33 |
maralorn | https://hydra.nixos.org/jobset/nixpkgs/haskell-updates trick: pick the mentioned commit from the eval three days ago | 12:23:38 |
dana | In reply to @maralorn:maralorn.de haskell-updates also gets cached, but there was a bag change today so you probably want a commit from a few days ago. Hmm, okay, thanks! I was trying to pull the last commit from the PR but it didn't have the cache.
What is a bag change? | 12:23:48 |
maralorn | A big change typed on my stupid phone. | 12:24:23 |
dana | big change - the default ghc upgrade from 429212? | 12:25:03 |
maralorn | Regarding staging-next I think that branch gets created fresh at some point the PR that you are looking for will be staging-next -> master. | 12:26:42 |
maralorn | * | 12:27:22 |
Alyssa Ross | It never gets recreated — staging just gets merged into it when it's time for a new cycle. | 12:33:19 |
dana | In reply to @qyliss:fairydust.space It never gets recreated — staging just gets merged into it when it's time for a new cycle. How can I find commits/PRs that correspond to this? | 12:35:33 |
| Marc Jakobi joined the room. | 12:37:24 |
Alyssa Ross | git log --merges --grep="staging.*staging-next" origin/staging-next would probably be reasonably accurate | 12:37:33 |
Alyssa Ross | Next staging-next won't be for at least a week, because we just started staging-next-25.05 | 12:38:11 |
dana | You mean this one, right? https://github.com/NixOS/nixpkgs/pull/429274
And no more commits will be added to it, only fixes? | 12:41:14 |
Alyssa Ross | I think you're confused — you asked how to find merges of staging into staging-next. That's a PR to merge staging-next into master. New commits can still be added to it, as long as they don't cause mass rebuilds on Hydra. | 12:48:40 |
dana | Ah, I see. I guess I thought staging-next is created alongside a PR to release/master and only fixes are merged into it. Thanks! | 12:52:40 |
Alyssa Ross | Staging is merged into staging-next, and then a staging-next to master PR is opened. New commits can still be added to staging-next after that as long as they don't cause rebuilds, or, rarely, if the rebuilds are judged to be worth it. | 12:54:52 |
| @dmjio:matrix.org joined the room. | 18:06:36 |
| 31 Jul 2025 |
| cartocor joined the room. | 08:41:04 |
| Sammy (It/Its) left the room. | 09:47:03 |
sterni (he/him) | First proper eval of Stackage LTS 24 / ghc 9.10.2 https://hydra.nixos.org/eval/1817278?compare=1817170 | 11:21:36 |
Pierre Thierry | I'm kephas on Github | 13:51:39 |