This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 14.4.0.0 instead.
Reason given by maintainers: Mistake in collections versions
EnOSlib-Ansible
enoslib-ansible repackages ansible (GPLv3) exclusively tailored for the EnOSlib project.
The rationale behind this is that ansible includes too much collections with regards to what is actually needed by the EnOSlib users.
Versionning
We follow the versionning numbers of the ansible package but we append an internal revision number. So for instance enoslib-ansible==7.5.0.1 repackages the same version of a subset of collections from ansible==7.5.0.
Each major version is kept in dedicated branch: for instance ansible_6 for repackaging ansible~=6.
Building
python setup.py bdist_wheelHow to add a new collection
Main branch
First, work in the main branch.
Add the collection as a submodule:
git submodule add https://github.com/ansible-collections/ansible.utils ansible_collections/ansible/utilsThis will register the collection with its latest commit, but don’t worry, we will specify a tag in a later step.
Edit setup.py to add the new collection to exclude_package_data (copy-paste existing ones)
Don’t bump the version in setup.py, otherwise you will have trouble cherry-picking later
Test that the package can be built:
python setup.py bdist_wheelCommit your changes
Release branches
Then for each version of Ansible we support (ansible_X branches):
git checkout ansible_X
Cherry-pick the commit from the master branch (with -x to track the source):
git cherry-pick -x a0b1c2d3e4f5Lookup which version of the collection should be included using ansible-build-data.
Tip: use git grep ansible.utils '*.deps' in the ansible-build-data repository
In general, use the latest minor version for the ansible version you target (e.g. ansible-7.7.0 for ansible_7)
For our example of ansible.utils, the result is 2.10.3
Update the submodule to the right tag:
(cd ansible_collections/ansible/posix/ && git checkout vX.Y.Z)Commit the change to the submodule
Bump version in setup.py: if there already was a release for the same Ansible version (e.g. 7.7.0.0), increase the fourth component (e.g. 7.7.0.1). Otherwise, just use the Ansible version with an additional 0.
Commit the version bump
Publish pip package: git tag vX.Y.Z.N and push, the CI will do the rest
Troubleshooting
If you are annoyed by local changes when changing branches, use git submodule update.
More info
This project is based on Antsibull project.
3 maintainers
Metadata
3 maintainers
Release files for enoslib-ansible 10.7.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| enoslib_ansible-10.7.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / enoslib_ansible-10.7.0.1-py3-none-any.whl
| Download URL | enoslib_ansible-10.7.0.1-py3-none-any.whl |
|---|---|
| Size | 3.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93f32e5b947759bd821bc39cf4ee570c92f9fe526cf1c3559ef4371828936b8e
|
|
BLAKE2b-256 checksum How to use checksums |
93d1fde8adc2afceb4dc15ec243b9a57dd77445cd378e80b660808adaf9a33c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
