Bug#1112261: trixie-pu: package ansible/12.0.0~b5+dfsg-0+deb13u1
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: ansible@packages.debian.org, debian@rocketjump.eu
Control: affects -1 + src:ansible
User: release.debian.org@packages.debian.org
Usertags: pu
(Please provide enough information to help the release team
to judge the request efficiently. E.g. by filling in the
sections below.)
[ Reason ]
This is an update to the latest ansible (ansible community collection) of the 12
series. ansible community is a collection of 100+ upstream collections that are
curated by the community manager. Collections usually provide users with
abstractions to use web APIs (e.g. azure, AWS, Hetzner hcloud), common
network appliances (Cisco, Juniper, Meraki), and also abstractions to e.g. DNS,
netblock calculators, etc. Collections included in the ansible community
collection adhere to certain quality standards and follow strict semantic
versioning as outlined in
https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html.
As such they add value to our users by providing curation work.
As mentioned in earlier unblock requests for ansible-core, I intend to track the
12 series during the lifecycle of trixie.
Between ~a6 and ~b5 a lot of collection were updated to work with ansible-core
2.19, which broke handling of internal variables and templating. As such,
updating the collection is useful to fix broken collections, and also prevent
some from emitting deprecation warnings.
[ Impact ]
If not approved, users will have older versions of ansible collection installed
that might not work with ansible-core 2.19.
[ Tests ]
Upstream has good tests, I also run all unit tests via autopkgtest prior to
upload. Max Vozeler <xam@debian.org> has also tested this package at work and
found no problems.
[ Risks ]
Since the ansible-core 2.19 release was postponed by 5 weeks shortly before the
release, ansible(-community) lagged behind a lot more than expected. As such the
list of changes are quite large for a point release. I however still believe
it's in the best interest for our users to track the 12.0.x series, as it is
supposed to go in tandem with ansible-core 2.19.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[ ] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The list of changes are documented here and I have checked all changes between
~a6 and ~b5, and approve them:
https://github.com/ansible-community/ansible-build-data/blob/main/12/CHANGELOG-v12.md#v12-0-0b5
[ Other info ]
The way ansible-community works creates huge debdiffs because the collection
manifests track checksums of every file. Also a few collections were renamed
(cisco.* namespace) which artificially inflates the debdiff to a wopping 82MB.
As such it is not attached and does not provide any meaningful insight.
If you have any follow-up questions don't hesitate to ask. I tried my best to
provide the info I think the release team needs to make a decision.
Reply to: