-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better handle new package names #67
Comments
Can you please post the generated ebuild? Mine generated correctly. |
|
Very odd. I'm on the same hackport version and don't have this issue. I'll keep an eye on it. Let me know if it occurs with other packages. I suspect it's trying to generate a dependency on |
Which hlint version is that? Can you attach actual |
This is not hlint, but hint-0.9.0.3, fetched from up-to-date hackage automagically. |
Yes, make-ebuild generates the same. |
Let's inline
|
I can't reproduce the failure either. Please provide a few details:
|
today's 9999 |
There are a few things we can do here:
|
Meanwhile you either need to fix the generated dependency manually or point hackport to an overlay with ghc package name. |
It generates it as
dev-haskell/ghc
while ghc lives in dev-lang. For example, tryhint
package from hackage.The text was updated successfully, but these errors were encountered: