Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
stackage-curator should have option to explain where broken deps are coming from #28
Twice this week I had to track down broken deps caused by some package update adding a new dep to a package which currently does not build in Stackage Nightly. It would be really nice if stackage-curator could show what packages are pulling in such breakage.
The two incidents were
The former was not so hard to track down with revdeps, but I had to go into all-cabal-hashes to hunt down the latter.
I'm hesitant to try adding this functionality to stackage-curator, as it's somewhat tricky to predict all pieces of information that would be desired. I typically resolve this by looking directly at the build-plan.yaml file, which lists the users of each package.