Your message dated Tue, 07 Nov 2023 16:19:14 +0000
with message-id <e1r0onk-00h7dr...@fasolo.debian.org>
and subject line Bug#1055394: fixed in python-pymemcache 4.0.0-6
has caused the Debian Bug report #1055394,
regarding src:python-pymemcache: fails to migrate to testing for too long:
autopkgtest regression on 32 bits
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.)
--
1055394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pymemcache
Version: 3.5.2-2
Severity: serious
Control: close -1 4.0.0-5
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:python-pymemcache has been trying to
migrate for 31 days [2]. Hence, I am filing this bug. The version in
unstable fails its own autopkgtest on 32 bit architectures: armel, armhf
and i386. armhf and i386 also fail on reproducible-builds.org with the
same test error.
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=python-pymemcache
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pymemcache
Source-Version: 4.0.0-6
Done: Thomas Goirand <z...@debian.org>
We believe that the bug you reported is fixed in the latest version of
python-pymemcache, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand <z...@debian.org> (supplier of updated python-pymemcache 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: Tue, 07 Nov 2023 16:48:36 +0100
Source: python-pymemcache
Architecture: source
Version: 4.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <team+openst...@tracker.debian.org>
Changed-By: Thomas Goirand <z...@debian.org>
Closes: 1055394 1055464
Changes:
python-pymemcache (4.0.0-6) unstable; urgency=medium
.
* Add remove-test-failing-on-32-bits.patch (Closes: #1055394).
* Remove (build-)depends on python3-six (Closes: #1055464).
Checksums-Sha1:
da5c2d5caa2f3a7e80a65f49ebee4fd5c8421666 2238 python-pymemcache_4.0.0-6.dsc
1d2b7f65e06f8dedb988c06cbe68565c5497cb20 5356
python-pymemcache_4.0.0-6.debian.tar.xz
8079ea9a1a34d609e81a56d3a4d6d71a271bd38f 7585
python-pymemcache_4.0.0-6_amd64.buildinfo
Checksums-Sha256:
42e7e8da5d365cf65d1cf53b424f5ef9a3ce76a34b617f853f9046f6901a2258 2238
python-pymemcache_4.0.0-6.dsc
faf8adc27215f7630c2731d01838757916dd3bc466c795e9f421a2c166edb3a5 5356
python-pymemcache_4.0.0-6.debian.tar.xz
380cdedd8f9e7b73b96a0e3e8aa690fbdfe0f8c5adfb4cb344248eb3ef9d29b4 7585
python-pymemcache_4.0.0-6_amd64.buildinfo
Files:
f60d9de50ccd9e1c66b8bf07192fba6b 2238 python optional
python-pymemcache_4.0.0-6.dsc
15cf0cdc69d1d730cfedf05c15f5b6b7 5356 python optional
python-pymemcache_4.0.0-6.debian.tar.xz
af39226c5da74f4f00ef7f95237be2c7 7585 python optional
python-pymemcache_4.0.0-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmVKXRQACgkQ1BatFaxr
Q/7ebA//aI8eu9igjw3+TWNGF3mlPhQ9km19orZZ+ezVNIw3apXsuAHY7IN5yEzz
sRSIqy7AqgB/NADmZFufbSB19gZ9cdPY7bVfL04JuOCRpT2z648VdkaSbIuX1w2f
kfATRcHdHtPSRwVmUNVt9RoYaLmsBk8ulg1v6905El/09AhPUBxyVmUNjbj0rebF
brX0r2YDRUO9r+E5xYsV3gDuMXBLqDrRS9PyylX4GmgzmnN5jQFYG8gGpt5JSm4Y
yPymkEAGHdO32m0EajnphiVVjmJXwLIc1Eq3mDjuxxsHfK4oRNi+tydNaKo0hDwb
IimuTPLHmROWphhpMmzs4fBnVrZncu+8HZFjC8NFPnLs+VHQxc+RcDb5OU3l24p4
70cTNUedMGGaRtyaTu7u1+dnBA5oElZ8ElH1TYv9oJ2biM6mUsykI5pMWTZsAKBj
pJdX389QDvKktAA7OCi8Qk5MAV9CyBhxN9cNmfb02ceZOc+Y2m6HYSCWc/KFGX/E
t/P/yk2lbGYQeNJ+zvIM/8qPEqipwQyDbknPz9yw1YG94Z9+SL+G5V8L6KacHUf/
KwIbjWfAHBOQfkMdjYIk8s/95xPizbqbL3t7pHxuBhePlWDQQFX5nzVamfxYhEw6
8PSnigwHaKAtjmyBu+veZIDeDbPxCrjrkKFzNxaFkY6qr7AdSsY=
=muPF
-----END PGP SIGNATURE-----
--- End Message ---
