Drop the dead ansible-lint < 5.0 pin from requirements-test.txt
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ansible, python
- Domain
- build-system, devops
Research direction
Open requirements-test.txt and confirm the ansible-lint < 5.0 line described in the issue. Remove that line, then check that the requirements file no longer installs the incompatible pin; done when the file contains no such pin.
Written by the indexing model from the issue text.
Description
requirements-test.txt pins ansible-lint < 5.0, but nothing uses that pin: CI runs pip install -r requirements-test.txt only to get tox, and tox's [testenv:ansible-lint] installs its own unpinned ansible-lint. The pinned 4.x release is also incompatible with current ansible-core (it fails on import with No module named 'ansible.parsing.yaml.constructor'), so anyone installing the file directly to lint locally gets a broken tool.
Remove the line. If a pin is wanted, it belongs in tox.ini next to the version tox actually installs.
- Dominant language
- Python
- Stars
- 9
- Forks
- 15
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from theforeman/obal
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
theforeman/obal#460 ·
Maintainers usually reply within 1 day
-
Add command to list available package groups from package_manifest.yamlPossibly taken @jakduch claimed this 20 days ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
theforeman/obal#427 ·
Maintainers usually reply within 1 day
-
Add command to list available packages from package_manifest.yamlPossibly taken @jakduch claimed this 20 days ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
theforeman/obal#426 · 2 comments ·
Maintainers usually reply within 1 day
-
Drop tito as a dependencyPossibly taken @ekohl claimed this 1026 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
theforeman/obal#294 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
theforeman/obal#256 ·
Maintainers usually reply within 1 day
Similar issues
-
md/asciidoc/csv: an explicit `encoding="utf-8"` keeps a leading BOM, the auto-detect path drops itOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
docling-project/docling#4846 ·
Maintainers usually reply within 1 day
-
area/sessions comp/dashboard comp/desktop comp/gateway comp/tui duplicate P2 sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#138914 · 1 comment ·
Maintainers usually reply within 1 day
-
bot-triaged module: activation checkpointing module: inductor oncall: pt2 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Update PR Actions Detective E2E prerequisites and fix dashboard-format table typoOpendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/oblt-aw#2382 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day