-
Notifications
You must be signed in to change notification settings - Fork 579
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
openSUSE packaging #2849
Comments
Some easier ones
Some harder ones
|
See https://build.opensuse.org/project/subprojects/home:jayvdb:coala for subprojects for various types of bears |
I would like to help but what exactly needs to be found here? A quick search at OpenSUSE package finder shows pyroma package under |
Most of the python bear linters have been packaged, or do exist https://build.opensuse.org/project/show/home:jayvdb:coala:python3-bears Other groups of linters can be found in sub-projects at https://build.opensuse.org/project/subprojects/home:jayvdb:coala |
https://build.opensuse.org/package/show/home:jayvdb:coala/python-coala-bears mostly works now, with the bear linters installed separately. |
There are unsolved issues about clang in bears and coala repos. I disabled those tests in the bears .spec |
node packaging is quite problematic, so we might leave those until last. The next big set is ruby, being collected at https://build.opensuse.org/project/show/home:jayvdb:coala:ruby-bears
RuboCop failures are the most important, and are probably related to other RuboCop failures (e.g. windows), however the ruby scss_lint is canonical and should be a high priority |
https://build.opensuse.org/project/requests/home:jayvdb:coala:python3-bears has a list of changes being made to get fix versions or resubmit 'misc' repo packages into main repo |
c.f. coala/coala#5972 for the coala task.
Collecting packages at https://build.opensuse.org/project/show/home:jayvdb:coala:python3-bears
I've found most of the top level dependencies.
Need to identify all the missing dependencies, and their sub-dependencies
The text was updated successfully, but these errors were encountered: