Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stackage set a package deprecated when Hackage does not #4734

Closed
QuietJoon opened this issue Jul 25, 2019 · 3 comments
Closed

Stackage set a package deprecated when Hackage does not #4734

QuietJoon opened this issue Jul 25, 2019 · 3 comments

Comments

@QuietJoon
Copy link
Contributor

I have added a package to Stackage two days ago.

However, Stackage set this package as deprecated. And I wait a day, but Stackage still does not refresh its information.

It has a deprecated version (0.4.1.1, not latest version) now, but I did it to reset/refresh Hackage or Stackage information after Stackage(nightly-19-07-24) had categorized the package as deprecated.

Is there any method to help refreshing the information of stackage about deprecation?
@cdornan
Copy link
Contributor

cdornan commented Jul 27, 2019

I agree that there appears to be a problem and am looking into it.

@cdornan
Copy link
Contributor

cdornan commented Jul 28, 2019

We will look at a fix for this later (on Monday).

@QuietJoon
Copy link
Contributor Author

Thanks, it seems to be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DanBurton @cdornan @QuietJoon