Open PhipBlitch-Arcadia opened 8 months ago
This will be some kind of dependency that has come through (from ansible-lint
or ansible
). This has actually been a consistent issue with managing older versions. I find it incredibly frustrating 😠 . I'll try to work out why it is happening.
I imagine that would be frustrating indeed! Thank you for building and maintaining this project - it is such a useful tool for bringing an old and neglected ansible project up to date!
I took another look, and it appears to be happening in the step
pip3 install --ignore-installed ansible-lint==${ANSIBLE_LINT}
which seems like a reasonable consequence of --ignore-installed
. However I assume it's there because without it this line blows up on ERROR: Cannot uninstall 'packaging'
.
I don't know if this would be sufficient for all the builds, but I was able to get the correct result under alpine:3.16 / 2.14.14 / 7.7.0 by freezing the packages up to that point into a requirements file:
pip3 install -r <(pip3 freeze) ansible-lint=${ANSIBLE_LINT}
In the 2.14-alpine- and 2.15-alpine- tags, It seems like something is pulling in the 2.16.4 version of ansible-core. pip3 reports the expected version, but the cli tools all report 2.16.4:
The pattern holds through the 2.15-alpine-* tags as well.
Non-alpine tags appear normal:
The 2.13-alpine-* tags also seem fine: