-
Notifications
You must be signed in to change notification settings - Fork 1.2k
packages for release 1.8.2 of why3 #28511
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
Conversation
This package provides the Coq realizations of Why3 theories.""" | ||
|
||
url { | ||
src: "https://why3.gitlabpages.inria.fr/releases/why3-1.8.2.tar.gz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
The URLs are unfortunately giving a 404 not found error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops! Fixed now. Can we restart the CI process?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regular CI restarted. But the windows one? I don't see how to do it. I even don't know at all if it would compiled under windows...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have opened this PR manually, you can just push the commit to claudemarche:master
(which I can see it was opened from), and the CI will run once again 👍
(when using opam publish, a rerun will also push to the same existing PR, but I suspect you are not using that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But there is no more changes to commit, the problem was on the server holding the source archive...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, now I understand: You fixed the receiving URL and made no changes here!
You can just close the PR and the press the 'Reopen PR' button. I believe that should restart the CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you've pressed rerun on the opam-ci page.
I don't have permissions to restart the GitHub Actions Windows workflow:
https://github.com/ocaml/opam-repository/actions/runs/17677129714/job/50241947001?pr=28511
Normally in the top right corner one can choose 'rerun failed' there...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that the CI reports incompatibilities with a few packages depending on Why3 but I can't do anything about it.
Could you proceed and accept the PR please ?
Would you consider adding |
Thanks for the suggestion. The dev team of Why3 will definitely consider this for the next minor release 1.9 |
I reopened this, as I expected you closed with the intention of a "close-reopen dance" to retrigger a CI run. Regarding the CI revdeps failures:
On Windows with a retriggered run:
|
Found it: It seems it was removed from the interface in the 1.8.2 release: |
This is a problem, that change was not intended to appear in the bugfix version 1.8.2. I'll fix this first in the source release, and then I'll come back to the OPAM packages. Better to close this PR now, I'll open a new one |
Just reopened the PR with fixed opam files corresponding to a fixed distribution. Let's wait for the CI now... |
The windows build for |
There are several lower-bounds failures during
The (Flashback to ~2-3 years ago when Kate stated that |
The other 2 errors are revdeps ones
which allows installing
Now installing llvm@17 with the former along with the latter described as Based on the above, I suggest merging this and working out the failures of the |
Thanks for the approval, thanks also for the useful feedback on the first commit. |
I agree, the conf packages lowerbounds are not a reason to not merge this. Proceeding Thanks both! |
new packages for new release 1.8.2 of why3