-
Notifications
You must be signed in to change notification settings - Fork 101
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
elogs 1.1.0 #957
elogs 1.1.0 #957
Conversation
Hi @kevlar700 , the tests are not running because the submitted file is at the wrong path: It should be at You can move the file to the proper location, commit and push in this same PR. |
Now the file has the correct name, but is still in the wrong location. The |
index/el/elogs-1.1.0.toml
Outdated
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.
This file should be removed
upload/index/el/elogs-1.1.0.toml
Outdated
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.
This file should be removed
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.
This file should be removed
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.
Sorry, the delete button was hidden. I didn't see the menu scroll bar for ages.
What is the issue now @mosteo ? |
Compilation is failing at the new
in the manifest. |
Do I need to remove -gnat2022 from here now? Does that require a new PR? Edit: I tried removing it but I see now that the failed LTS checks use a distro toolchain that doesn't support 2022. Not sure what is happening with alr dev. A pretty cool set of checks :) |
The
This means you need a minimum compiler version dependency. I'll add that one because I also have to deal with the error with compiling the master branch; bizarrely I suspect a PR intended to ensure wide compiler compatibility may have introduced that regression. So I think you're done, thanks for the patience |
Remaining checks should succeed after alire-project/alire#1566 is merged |
No description provided.