-
Notifications
You must be signed in to change notification settings - Fork 7
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
wstunnel package needs restricted bounds #265
Comments
Is there an upstream issue? We hope that maintainers (learn to) make revisions. The both |
I couldn't find the upstream. The package points to https://github.com/githubuser/wstunnel but the link gives a 404 not found error.
Is there anything I can do? |
upstream bug: erebe/wstunnel#45 |
the maintainer says he can't reupload the same version to add bounds :-( |
It seems like erebe/wstunnel#45 is resolved, can this be closed? |
@vaibhavsagar I don't consider the package in a good shape yet; it's mostly the metdata that's seriously lacking:
And last but not least the author isn't aware of metadata revisions and believes you can't fix these things and can only upload new releases (which obviously don't fix the problem since the solver can still backtrack and access the previous releases). Unfortunately, this isn't a single incident; this has become a common theme (To give you a hint of the extent of the problem: 3 years ago I already compiled a list of over 500 packages which suffered from stack-template-prefilled boilerplate |
bearing in mind the above comment, I don't think that's stuff that's directly actionable in this repo, so optimistically (or pessimistically?) closing |
It was suggested to me to come here but I'm not sure if this the right place to report this. Apologies if not!
I couldn't find any contacting information... so never
There is no issue tracker
I've recently switched to Ghcup and it's my understanding that
cabal install wstunnel-0.3.0.0
should install the package. However, this is what I ended up withThis is not critical to me.
The text was updated successfully, but these errors were encountered: