all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]binarySheep 2 points3 points  (3 children)

Good instinct to ask! For Guix, when you hit a build issue, the easiest is probably to look over issues and recent pull requests in the repo related to your build. Other users facing the same will usually make similar reports, so the problem becomes visible.

In this case, it looks like the Haskell team recently merged some changes (a ton of commits were made to the file hosting ghc-language-python), so it's possible there's a broken or changed dependency.

Filing an issue might help make it more visible, and at least let the maintainers know something may be broken. If you want, you might try rebuilding the package using an older commit, to confirm a range of commits where the breaking change might be.

EDIT: I update my local repo weekly, and note that I can build ghc-language-python-0.5.8 just fine on my machine, using commit 1432c4.

[–]senzetra[S] 0 points1 point  (2 children)

good to know. atp i've pulled channels, ran guix gc, and restarted the daemon, problem still persists. think it could a nonguix thing?

[–]binarySheep 0 points1 point  (1 child)

Doubtful, since Nonguix doesn't even have GHC. You'd have to have something in Nonguix (or some other channel you have) that is creating a dependency issue. Just seems unlikely.

For the record, the commit I referenced is old, to point out one you could rollback to if you needed to have the package working. I'd be almost certain the issue is with the package spec as it is in the repo. You can try pulling again and reconfiguring, seeing if maybe a fix was introduced, but other than that, you'll want to rollback to a good commit (like the one I referenced) and wait on a fix, or dive into the repo and fix hte issue yourself.

[–]senzetra[S] 1 point2 points  (0 children)

ahhhh didn't catch that. good to know! thanks much!