You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #792, the github action that's currently being used as a linter is failing due to it being unable to install "libenchant-dev". I believe the solution to this would be changing "libenchant-dev" to "libenchant-2-dev", since it seems that this is the replacement, but I'm unable to test it on my end.
To Reproduce
Create a fork
Change something in fork (add comment) and push to fork.
Try to merge fork
Wait for maintainers to permit testing
Fail pylint check (incorrectly)
Expected behavior
The linter should run on the PR and correctly check the commit.
Logs/tracebacks
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libenchant-devError: Process completed with exit code 100
Python Version
$ python --versionPython 3.10.6
multidict Version
$ python -m pip show multidictName: multidictVersion: 6.0.3
yarl Version
$ python -m pip show yarlName: yarlVersion: 1.8.2
OS
Linux virtual environment.
Additional context
No response
Code of Conduct
I agree to follow the aio-libs Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
As mentioned in #792, the github action that's currently being used as a linter is failing due to it being unable to install "libenchant-dev". I believe the solution to this would be changing "libenchant-dev" to "libenchant-2-dev", since it seems that this is the replacement, but I'm unable to test it on my end.
To Reproduce
Expected behavior
The linter should run on the PR and correctly check the commit.
Logs/tracebacks
Python Version
multidict Version
yarl Version
OS
Linux virtual environment.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: