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.

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

Adabots 1.9.0 #1108

Merged
merged 3 commits into from
Oct 14, 2024
Merged

Adabots 1.9.0 #1108

merged 3 commits into from
Oct 14, 2024

Conversation

TamaMcGlinn
Copy link
Contributor

No description provided.

@Fabien-Chouteau
Copy link
Member

It looks like json_ada doesn't compile with GNAT FSF 14:

json-streams.ads:32:29: error: function cannot have parameter of mode "out" or "in out" in SPARK [E0015]

@Fabien-Chouteau
Copy link
Member

Hi @onox, GNAT FSF 14 is now checking more SPARK restrictions. Like this one:

json-streams.ads:32:29: error: function cannot have parameter of mode "out" or "in out" in SPARK [E0015]

We will have to specify a gnat dependency on the json_ada releases.

@onox
Copy link
Contributor

onox commented Jul 22, 2024

We will have to specify a gnat dependency on the json_ada releases.

Thanks for mentioning this. Tracked in onox/json-ada#12. I'll try to fix it this weekend to unblock this PR ASAP.

@onox
Copy link
Contributor

onox commented Jul 28, 2024

I have openend #1164. json v6.0.0 should compile with GNAT < 14.

Copy link

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Sep 27, 2024
@mosteo
Copy link
Member

mosteo commented Sep 27, 2024

json-streams.ads:32:29: error: function cannot have parameter of mode "out" or "in out" in SPARK [E0015]
json-streams.ads:32:29: error: launch "gnatprove --explain=E0015" for more information

@TamaMcGlinn
Copy link
Contributor Author

Ah, I think the issue may be that I was trying to release for alire 1.3.0 - but I am currently using 1.2.2 and actually, alire 1.3.0 isn't even in the releases list. I don't understand why there is even a 1.3.0 branch at all.

@github-actions github-actions bot removed the Stale label Sep 28, 2024
@mosteo
Copy link
Member

mosteo commented Sep 30, 2024

I don't understand why there is even a 1.3.0 branch at all.

Hi Tama. That's because the versioning of the index and of Alire aren't the same. The latest index format version is 1.3.0, the latest Alire is 2.0.1. Which index versions are understood by Alire is shown by alr version.

But I don't think that's related to the errors, which seem to come from more recent versions of the toolchain being more restrictive.

@mosteo
Copy link
Member

mosteo commented Oct 14, 2024

Hi @TamaMcGlinn, I've re-run the tests with updated Docker images and our latest alr release and there are no issues remaining, so I'm merging this PR. Thanks for the patience.

@mosteo mosteo merged commit 7770d51 into alire-project:stable-1.3.0 Oct 14, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants