-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Some packages with broken upstreams #12421
Comments
Other ones too:
|
these should realistically be yanked out - I don't expect there are any users, and there were a significant number of bugs. The more recent versions (hosted at github) may however be of use to someone. Forgive me for my ignorance of the contribution model, I couldn't find this info easily - is removal of old versions allowed?
|
The binary file for |
Thanks @jnfoster @arjunguha ! |
New check:
|
The Frenetic is fixed now, and fail-safe'd so we won't delete the tarball again. Sorry about that! |
This issue is stale because it has been open 90 days with no activity. Remove the stale label, or comment, or this will be closed in 15 days. |
New check:
|
The obandit package tarballs should be fixed by #16610 . With apologies for the time this took. |
new new check
|
Definitely yank the |
new check, new list
|
|
|
new check
|
YAC (yet another check)
|
Thanks for the updates. In the process of the opam repository archiving, I fixed all the archives (or marked the packages as unavailable). Of course this does not mean there won't be any new ones ever ;) -- I'll close this issue, please if you have updated reports report a fresh issue and we can deal with them immediately (opam.robur.coop/cache should contain all the existing tarballs). |
Just following-up on the logs of opam-repository:
The text was updated successfully, but these errors were encountered: