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

Bug#984557: marked as done (unblock: ansible-base/2.10.5+dfsg-1)



Your message dated Wed, 17 Mar 2021 09:55:00 +0200
with message-id <CAM8zJQuUmqB0i3XL3FYh8i7gw0K+4hmrYS0=zdNa008dc8=png@mail.gmail.com>
and subject line Re: Bug#984557: unblock: ansible-base/2.10.5+dfsg-1
has caused the Debian Bug report #984557,
regarding unblock: ansible-base/2.10.5+dfsg-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.)


-- 
984557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984557
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian@rocketjump.eu, hlieberman@setec.io

Please unblock package ansible-base

[ Reason ]
Due to missing upload ACLs I unfortunately missed the soft freeze by a few days.

With 2.10, upstream ansible is split into two parts, "ansible-base" and
"ansible". This split is also reflected in the two source/binary packages of the
same name in Debian. ansible-base is a hard-dep for ansible. I've personally
been using the split packages for over two months now, and I've tested upgrades
and of course used the package extensively. The packages have also been in
experimental for about 6 weeks, and have been tested by several volunteers.

2.10 comes with support for ansible collections, which is the new format with
which 3rd party modules/plugins are be shipped. With 2.9 currently in testing
users won't be able to use those (as collection support is incomplete in 2.9).

The next 2.10 upload will also come with autopkgtests which I have been working on
for the last month.

[ Impact ]
If the unblock is not granted, I will have to upload an epoch version 2:2.9.16-1
to revert the ansible package in unstable, and ansible will ship with an older
version.  Backporting security fixes will be more difficult, as I'd have to
correlate the changes of 2.10+ with the pre-split code of 2.9 after upstream
security support runs out. Ansible-base 2.10 will also have about 12 months
longer upstream security support than ansible 2.9, depending on the release
schedule of 2.11+.

[ Tests ]
Automated tests is piuparts currently, which runs through fine. Manual tests
involve running my personal playbook against my server fleet. With the next 2.10
upload there will be working autopkgtests that I've been working on for the last
month.

[ Risks ]
ansible/ansible-base are leaf packages, with only ansible-lint and
ansible-mitogen depending on those.

ansible-lint works fine without changes. ansible-mitogen will need an update
that's already packaged in experimental.

[ 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 testing
  -> doesn't apply as currently not included in testing.

[ Other info ]
(Anything else the release team should know.)

unblock ansible-base/2.10.5+dfsg-1

--- End Message ---
--- Begin Message ---
Hi Lee

On Fri, 5 Mar 2021 at 02:12, Lee Garrett <debian@rocketjump.eu> wrote:
Please unblock package ansible-base

I'm sorry, this was too late.

Arguably, a change like this should even have been in before the transition freeze on 2021-01-12.

Regards
Graham


--- End Message ---

Reply to: