c2c0edfae4
A change in Ansible 6, discussed at [1], highlights that Ansible is using the #! line to determine using it's own heuristics the interpreter to use to run the file, rather than the more common idea that this file is being interpreted by the kernel. The best solution seems to be to have no interpreter line, which is done here. To avoid confusion this removes the executable bit; if you want to run it manually you should run it under the python binary as an argument. I couldn't find any other instances of this same behaviour in system-config. [1] https://github.com/ansible/ansible/issues/78809 [1] |
||
|---|---|---|
| .. | ||
| defaults | ||
| library | ||
| tasks | ||
| README.rst | ||
Create git repos on a gitea server
Role Variables