Your message dated Sat, 15 Nov 2025 11:21:45 +0000 with message-id <736c7150dc08501cc89945035c406eaf9688e144.camel@adam-barratt.org.uk> and subject line Closing requests for updates included in 13.2 has caused the Debian Bug report #1112261, regarding trixie-pu: package ansible/12.0.0~b5+dfsg-0+deb13u1 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.) -- 1112261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112261 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: trixie-pu: package ansible/12.0.0~b5+dfsg-0+deb13u1
- From: Lee Garrett <debian@rocketjump.eu>
- Date: Thu, 28 Aug 2025 00:52:54 +0200
- Message-id: <175633517442.244927.286783587216512562.reportbug@batou>
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.
--- End Message ---
--- Begin Message ---
- To: 1110859-done@bugs.debian.org, 1111236-done@bugs.debian.org, 1111733-done@bugs.debian.org, 1111734-done@bugs.debian.org, 1111808-done@bugs.debian.org, 1111819-done@bugs.debian.org, 1112097-done@bugs.debian.org, 1112120-done@bugs.debian.org, 1112256-done@bugs.debian.org, 1112261-done@bugs.debian.org, 1112276-done@bugs.debian.org, 1112282-done@bugs.debian.org, 1112283-done@bugs.debian.org, 1112380-done@bugs.debian.org, 1112479-done@bugs.debian.org, 1112557-done@bugs.debian.org, 1112668-done@bugs.debian.org, 1112671-done@bugs.debian.org, 1113711-done@bugs.debian.org, 1113750-done@bugs.debian.org, 1113757-done@bugs.debian.org, 1113761-done@bugs.debian.org, 1113778-done@bugs.debian.org, 1113799-done@bugs.debian.org, 1113804-done@bugs.debian.org, 1113860-done@bugs.debian.org, 1113882-done@bugs.debian.org, 1113902-done@bugs.debian.org, 1113904-done@bugs.debian.org, 1113961-done@bugs.debian.org, 1113979-done@bugs.debian.org, 1114595-done@bugs.debian.org, 1114684-done@bugs.debian.org, 1114755-done@bugs.debian.org, 1114855-done@bugs.debian.org, 1114929-done@bugs.debian.org, 1114979-done@bugs.debian.org, 1115257-done@bugs.debian.org, 1115486-done@bugs.debian.org, 1115530-done@bugs.debian.org, 1115749-done@bugs.debian.org, 1115815-done@bugs.debian.org, 1115860-done@bugs.debian.org, 1115899-done@bugs.debian.org, 1115914-done@bugs.debian.org, 1116012-done@bugs.debian.org, 1116020-done@bugs.debian.org, 1116040-done@bugs.debian.org, 1116053-done@bugs.debian.org, 1116127-done@bugs.debian.org, 1116196-done@bugs.debian.org, 1116201-done@bugs.debian.org, 1116386-done@bugs.debian.org, 1116523-done@bugs.debian.org, 1116526-done@bugs.debian.org, 1116547-done@bugs.debian.org, 1116575-done@bugs.debian.org, 1116665-done@bugs.debian.org, 1116705-done@bugs.debian.org, 1116938-done@bugs.debian.org, 1116945-done@bugs.debian.org, 1116983-done@bugs.debian.org, 1117467-done@bugs.debian.org, 1117469-done@bugs.debian.org, 1117828-done@bugs.debian.org, 1117843-done@bugs.debian.org, 1117876-done@bugs.debian.org, 1117909-done@bugs.debian.org, 1118008-done@bugs.debian.org, 1118037-done@bugs.debian.org, 1118047-done@bugs.debian.org, 1118228-done@bugs.debian.org, 1118374-done@bugs.debian.org, 1118434-done@bugs.debian.org, 1118443-done@bugs.debian.org, 1118458-done@bugs.debian.org, 1118547-done@bugs.debian.org, 1118657-done@bugs.debian.org, 1118663-done@bugs.debian.org, 1118673-done@bugs.debian.org, 1118674-done@bugs.debian.org, 1118737-done@bugs.debian.org, 1119085-done@bugs.debian.org, 1119088-done@bugs.debian.org, 1119115-done@bugs.debian.org, 1119136-done@bugs.debian.org, 1119142-done@bugs.debian.org, 1119256-done@bugs.debian.org, 1119286-done@bugs.debian.org, 1119287-done@bugs.debian.org, 1119288-done@bugs.debian.org, 1119291-done@bugs.debian.org, 1119301-done@bugs.debian.org, 1119303-done@bugs.debian.org, 1119719-done@bugs.debian.org, 1119798-done@bugs.debian.org, 1119854-done@bugs.debian.org, 1119909-done@bugs.debian.org, 1120048-done@bugs.debian.org, 1120050-done@bugs.debian.org, 1120054-done@bugs.debian.org, 1120125-done@bugs.debian.org, 1120129-done@bugs.debian.org, 1120143-done@bugs.debian.org, 1120145-done@bugs.debian.org, 1120148-done@bugs.debian.org, 1120151-done@bugs.debian.org, 1120262-done@bugs.debian.org, 1120278-done@bugs.debian.org, 1120289-done@bugs.debian.org, 1120325-done@bugs.debian.org, 1120345-done@bugs.debian.org, 1120350-done@bugs.debian.org, 1120358-done@bugs.debian.org, 1120360-done@bugs.debian.org, 1120445-done@bugs.debian.org
- Subject: Closing requests for updates included in 13.2
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sat, 15 Nov 2025 11:21:45 +0000
- Message-id: <736c7150dc08501cc89945035c406eaf9688e144.camel@adam-barratt.org.uk>
Package: release.debian.org Version: 13.2 Hi, The updates referenced in each of these bugs were included in today's 13.2 trixie point release. Regards, Adam
--- End Message ---