[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1110092: marked as done (unblock: ansible-core/2.19.0-1)

Your message dated Thu, 14 Aug 2025 13:52:43 +0200
with message-id <906e549b-f761-4c21-b196-54e704c4bee0@debian.org>
and subject line close all open unblock requests, the trixie release happened
has caused the Debian Bug report #1110092,
regarding unblock: ansible-core/2.19.0-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1110092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110092
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Hi,
I'm sorry we couldn't unblock your request in time for trixie. I'm closing all open unblock requests in one go, so I'm not going into details of the particular request, but reasons are typically as follow: 
- the request came after the deadline of 2025-07-30
- the request came late and we just didn't have the time to deal with it
- the request was waiting for action from the submitter (moreinfo tag)
- the request didn't appear to be in line with the freeze policy and we
  didn't have the energy to engage (sorry for that, see our FAQ [1])
- there was discussion in the unblock request but no agreement was
  reached in time for the release.

Paul

[1] https://release.debian.org/trixie/FAQ.html

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: