-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
OSError: File coala.yaml does not exist #365
Comments
it seems to me that coala.yaml file was not available in current directory. overrides uses file system 2 syntax to refer to file link, here is an example:
|
which version works? I suspect the ones before file system 2 integration. |
coala.yaml isnt in the current directory of https://gitlab.com/coala/package_manager . https://gitlab.com/coala/mobans/ is fetched prior to invocations of moban, and placed in the appropriate directory, so that coala.yaml can be found. This worked in v0.5.0 at least; im not sure which versions after that worked.
I know about the new features. Is the system I am using no longer going to be supported? |
I will find a time to provide backward compatibility. |
reproduced. 0.6.4 still worked. |
Latest 0.7.1 will work for you. |
if possible, please contribute a regression test for your use case. |
There has been some regression, or some functionality has been decommissioned.
https://gitlab.com/jayvdb/package_manager/-/jobs/498590570
The structure is https://gitlab.com/coala/package_manager/-/blob/5f33f1f9/.moban.yaml is used first , and it overrides https://gitlab.com/coala/package_manager/-/blob/5f33f1f9/pm-requirements.yaml , which overrides coala.yaml , which was previously found via
configuration_dir: ../coala-mobans
from.moban.yaml
.The same structure is used throughout all coala repos CI, so this halts development until fixed somehow. If we need to update the syntax, it is possible but a large task and a bit undesirable.
The text was updated successfully, but these errors were encountered: