-
Notifications
You must be signed in to change notification settings - Fork 5
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
Release 1.0.11 #11
Comments
I'm attempting to do this but opam release keeps giving me unhelpful
errors. Will get to the bottom of this soon.
…On Fri, May 26, 2023, 02:46 Célestin Matte ***@***.***> wrote:
Hello,
Can you create a release for 1.0.11, so I can update the arch linux
package?
(There currently is a build issue, not sure if it's already handled by the
latest commits)
—
Reply to this email directly, view it on GitHub
<#11>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABA653JQA7RWDFTMHNSG2TXIB3VVANCNFSM6AAAAAAYP7XCQI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hello, any update on this? |
I get this error when I try
My strategy of waiting for stuff to fix itself has failed. Let me ping support channels. |
@Perdu do you want to try to release this? Just clone it and try I've tried two different opam environments on two different machines and am having no luck. |
For some reason, I get |
ping |
opam-repository maintainers ask for the reason for the |
Oh. That's weird. I don't know why there isn't a 1.0.11 release on github. |
I guess I thought you meant do an opam release when you said create a release, but you were saying just create a github release. |
So, if I had known more about Arch Linux this might have been less confusing. Whoops! Anyway! Release created: https://github.com/mbacarella/curses/releases/tag/1.0.11 Re-open if I missed anything. |
Hello,
Can you create a release for 1.0.11, so I can update the arch linux package?
(There currently is a build issue, not sure if it's already handled by the latest commits)
The text was updated successfully, but these errors were encountered: