Your message dated Wed, 16 Oct 2024 01:19:29 +0000
with message-id <e1t0shf-00bhi9...@fasolo.debian.org>
and subject line Bug#1079672: fixed in ansible-core 2.17.5-1
has caused the Debian Bug report #1079672,
regarding src:ansible-core: fails to migrate to testing for too long:
autopkgtest regression
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 ow...@bugs.debian.org
immediately.)
--
1079672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ansible-core
Version: 2.17.1-1
Severity: serious
Control: close -1 2.17.3-1
Tags: sid trixie
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package src:ansible-core has been trying to migrate
for 31 days [2]. Hence, I am filing this bug.
The version in unstable fails its own autopkgtest.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and trixie, so
it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=ansible-core
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ansible-core
Source-Version: 2.17.5-1
Done: Colin Watson <cjwat...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ansible-core, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated ansible-core package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 16 Oct 2024 01:57:21 +0100
Source: ansible-core
Architecture: source
Version: 2.17.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1078779 1079672
Changes:
ansible-core (2.17.5-1) unstable; urgency=medium
.
* Team upload.
* New upstream release:
- copy module now updates mtime/atime (closes: #1078779).
* Skip "raw" integration test, since it requires su (closes: #1079672).
Checksums-Sha1:
d45c77eec10ce80420250c7e6d4ccb76fec17d9e 2593 ansible-core_2.17.5-1.dsc
0ad7fe8a78a2551201796ec571f6c19b0d0bba92 3097858
ansible-core_2.17.5.orig.tar.gz
0940ab8fde82fa2ac4920d1c7a01a3b44caba41c 22768
ansible-core_2.17.5-1.debian.tar.xz
Checksums-Sha256:
3954d68b8c94ee42466a54618079012d27059630803759e2c42786a26478f548 2593
ansible-core_2.17.5-1.dsc
ae7f51fd13dc9d57c9bcd43ef23f9c255ca8f18f4b5c0011a4f9b724d92c5a8e 3097858
ansible-core_2.17.5.orig.tar.gz
715fa16f16e36e2bba716aafbd383bdf1e4ec54a0d0e3f3e8c9635c9a940c93f 22768
ansible-core_2.17.5-1.debian.tar.xz
Files:
24852070ab686b8e129a2cdbf0e68a8f 2593 admin optional ansible-core_2.17.5-1.dsc
3d90bd7a14eae29f55435f77172e1edb 3097858 admin optional
ansible-core_2.17.5.orig.tar.gz
cf2daa709e6af3c4eedd0b48b77a9efd 22768 admin optional
ansible-core_2.17.5-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmcPEDAACgkQOTWH2X2G
UAvvzQ/7B2pAZtA9D76zNLMCOyPIEs1ZBQcK87GygKUSPqLuuvj20J67KWayOgjx
+VXpH2Ut4EYU6Ut1KgPPb8/8UJGz0I0WfhEs5OrmzGLxIrBN8zPDJT+VrDu8RgQC
45S1ybbpobCLb1WuTs9IrGF3R6TC8choVc/K2NPfKVlhfaIcH0XLDWcLiXjKf5Oe
iMNshJvHKty4NH8hWwfq9MnlEDTV2fBxK7kjOUF1DfCBWkXoQieS8Dq/Ophv8wN1
/S2Zdn1b/twKwaAfVNIop/g2zQX7IF2Iwqe6msnsIW2RH9cv/ReRndsa8f5WtNRk
HT+rz+zvyP9KtgD8fW/6Q7mRySoQqDFb/J5gGya3/JqcWmSBFC8Pr9TeGUNmgftI
TUrea0/5fjDjIRX9j9lrjR5XnOUJ0w668PUbgPo6LjWyDMQsjS5fogNgclDSKT3/
1cPdhndPcf71cvB2ZMZBno5QWtKbQEAFdFaVIzCZuCztlAKJUfAKUApWWHBvYp2v
Jk7t8WERj4UwqHdMrFbEYsi1WxC5aC0TZJnAmyfnmiz5S7lwQBXxrATlUFZjLs2x
ewKXD4l0GTamP2/pWCWHiFBSLN/2g/oeiZH/6RHBAXmyIoeVEYiCo5swIj6puP5D
Nh4/BaKtPrZ2rIRgbfHpKZJGRDwXVKEcun8YGronO01ADW5NwpA=
=EgvK
-----END PGP SIGNATURE-----
pgpv4VX6bXQmb.pgp
Description: PGP signature
--- End Message ---
