Bug#1110092: unblock: ansible-core/2.19.0-1
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: ansible-core@packages.debian.org, debian@rocketjump.eu
Control: affects -1 + src:ansible-core
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package ansible-core
[ Reason ]
This is the final 2.19.0 release of ansible-core. It contains a bunch of
fixes/deprecations from beta7 (I unfortunately missed those from d/changelog), 4
bugfixes in rc1, and added 12 deprecation warnings in rc2. rc2 and the final
release are identical in code, the latter just aggregated the changelog.
[ Impact ]
(What is the impact for the user if the unblock isn't granted?)
There's at least one bug reported by Martina Ferrari which was fixed in rc1:
https://bugs.debian.org/1106362 (3 issues in total)
https://github.com/ansible/ansible/issues/85204
There are also a handful of deprecations in the final release which I believe
users should see now, so they can migrate away from those before forky.
[ Tests ]
(What automated or manual tests cover the affected code?)
The test coverage is stellar in Debian, a bunch of tests were added between
~beta7 and the final release. Upstream also runs tests against other distros and
OSes which we cannot cover via autopkgtests.
[ Risks ]
The debdiff is larger than I'd like it to be, but ansible-core is a huge
project, and I believe following upstream here is safer than cherry-picking
patches because upstream can test against other OSes. I'm not aware of any
issues that this unblock can cause, and I take personal responsibility for any
breakage, and will fix anything caused by it in a timely manner should an issue
arise.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
(Anything else the release team should know.)
unblock ansible-core/2.19.0-1
Reply to: