Haskell in Nixpkgs/NixOS - Public Room Timeline

	Haskell in Nixpkgs/NixOS	700 Members
	For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs \| Current Docs: https://nixos.org/manual/nixpkgs/unstable/#haskell \| Current PR: https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates \| Maintainer Docs: https://github.com/NixOS/nixpkgs/blob/haskell-updates/pkgs/development/haskell-modules/HACKING.md \| More Nix: #community:nixos.org \| More Haskell: #haskell-space:matrix.org \| Merger Schedule: https://cloud.maralorn.de/apps/calendar/p/H6migHmKX7xHoTFa/dayGridMonth/now \| Join #haskell.nix:libera.chat for question about the alternative haskell.nix infrastructure	137 Servers

Sender	Message	Time
21 Feb 2026
	h7x4 changed their profile picture.	19:30:15
	h7x4 changed their profile picture.	19:33:40
22 Feb 2026
	Kite joined the room.	02:54:14
aiya	so for this section of the maintainer guide, and the fact that the filter for current PRs (https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates) includes `head:haskell-updates`, does that imply any PR must start with `haskell-updates`? or not (https://github.com/NixOS/nixpkgs/pull/487958)?	05:50:21
Alex	I don't know how GitHub's PR rules work, but I believe `head:haskell-updates` filters for all PRs targeting the `haskell-updates` branch. The Nixpkgs convention for PR titles is to title them with the affected package. My PR there is a bit of an irregular one because while it does modify a `ghc` package (`pkgsCross.riscv64.haskell.compiler.ghc94`), it does not touch the default `ghc`. It targeted `haskell-updates` because it was a fix to a regression in a build checked by Hadrian.	06:10:16
hellwolf	hmm, what happens to https://nixpk.gs/pr-tracker.html?pr=485516 ?	15:32:43
alexfmpe	I don't understand the question	15:55:58
hellwolf	sorry for my Sunday laconism :p I meant to ask when will that haskell-updates PR be merged to master/nixpkgs-unstable?	17:33:04
maralorn	Well, when it's finished. 😆 I have no clue if there is a holdup on staging-next. Coordination around that question happens in the staging chat room.	17:41:07