!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

740 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/ | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org146 Servers

Load older messages


SenderMessageTime
22 Feb 2026
@hellwolf:matrix.orghellwolfsorry 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:maralorn.demaralornWell, 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
@aiya:catgirl.cloudaiya

i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg

I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch

i believe that would be base:haskell-updates, head filters on your branch name

22:41:57
@maralorn:maralorn.demaralorn aiya: I am not aware of any rule. At least when you are opening the PR from your fork. 22:50:49
23 Feb 2026
@acidbong:envs.netAcid Bong
In reply to @aiya:catgirl.cloud

i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg

I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch

i believe that would be base:haskell-updates, head filters on your branch name

your branch name doesn't matter at all, only commit and PR description and contents
20:12:06
@acidbong:envs.netAcid Bong* your branch name doesn't matter at all, only commit and PR description and contents, and the branch you're targeting20:13:29
@magpi:matrix.orgLuke changed their display name from magpi to Luke Worth.21:17:08
@magpi:matrix.orgLuke changed their display name from Luke Worth to Luke.21:17:40
24 Feb 2026
@noiobeforebedtime:winesj.comJackโ€‹ changed their profile picture.03:32:21
25 Feb 2026
@sternenseemann:systemli.orgsterni (he/him) chreekat: I'm wondering now if you'll be quicker to redeploy all-cabal-tool or I in migrating hackage2nix to the cabal-install db :p 17:23:53
@sternenseemann:systemli.orgsterni (he/him) * chreekat: I'm wondering now whether you'll be quicker to redeploy all-cabal-tool or I in migrating hackage2nix to the cabal-install db :p 17:24:08
@b:chreekat.netchreekatfun idea17:47:47
@b:chreekat.netchreekati'll deploy tomorrow :p17:47:54
@b:chreekat.netchreekati have another client whose whole system just exploded for god knows why. keeps me occupied17:48:16
@maralorn:maralorn.demaralornProbably a client who pays better than us. (Seeing that we are not paying you at all.) ๐Ÿ˜„17:49:58
@b:chreekat.netchreekatHF pays :318:16:49
@maralorn:maralorn.demaralornProbably still not as good as the other client. ๐Ÿ˜†18:21:56
@dandart:matrix.orgEmber Void changed their display name from Void Mona(d) to Void Ember.19:11:27
26 Feb 2026
@b:chreekat.netchreekat sterni: https://github.com/commercialhaskell/all-cabal-hashes/commit/e89f69681f6366e77ab017b8b496c4ee2c6825b5 10:19:40
@sternenseemann:systemli.orgsterni (he/him)great thank you! did not get my change cleaned up in timeโ€ฆ11:44:39
@b:chreekat.netchreekatYou should use casa! It also needs an update, but it's the superior, undocumented choice to all-cabal-hashes imo12:37:51
@b:chreekat.netchreekatI'm gonna get it (casa.stackage.org) up to speed next12:38:33
@sternenseemann:systemli.orgsterni (he/him)is it documented anywhere?13:42:26
@sternenseemann:systemli.orgsterni (he/him)but I do not think we actually need it, the hackage index has everything we need nowadays as long as the index state timestamp is reliable but should be ok13:43:03
@b:chreekat.netchreekatJust a couple old blog posts13:44:51
@b:chreekat.netchreekat Interesting. I did not know you could just go straight to hackage now. I know that casa solved problems when it was developed, the same problems all-cabal-hashes was supposed to solve 13:50:12
@teoc:matrix.orgTeo (he/him)I think the issue that all-cabal-hashes solves (for nix) is that you want to map a package name and revision to a cabal file hash at nix eval time, which I don't think you can do with casa without IFD14:29:34
@b:chreekat.netchreekatTrue, you probably need dynamic drvs in order to follow the chain from a fod that pulls the top of the tree to all the other fods that describe the package source15:25:26
@maralorn:maralorn.demaralornDynamic drvs are not allowed on hydra, are they?15:27:14
@b:chreekat.netchreekatI assume not, but at least it's theoretically more pleasing than ifd15:36:57

Show newer messages


Back to Room ListRoom Version: 6