Your message dated Thu, 16 Jul 2020 03:48:40 +0000 with message-id <e1jvusy-00074t...@fasolo.debian.org> and subject line Bug#964299: fixed in m2crypto 0.36.0-1 has caused the Debian Bug report #964299, regarding src:m2crypto: fails to migrate to testing for too long: unfixed RC bug and maintainer built arch:all binaries 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.) -- 964299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: m2crypto Version: 0.31.0-9 Severity: serious Control: close -1 0.35.2-2 Tags: sid bullseye User: release.debian....@packages.debian.org Usertags: out-of-sync Control: block -1 by 959947 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:m2crypto in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. 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 bullseye, 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/2020/02/msg00005.html [2] https://qa.debian.org/excuses.php?package=m2crypto
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Source: m2crypto Source-Version: 0.36.0-1 Done: Sandro Tosi <mo...@debian.org> We believe that the bug you reported is fixed in the latest version of m2crypto, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi <mo...@debian.org> (supplier of updated m2crypto 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, 15 Jul 2020 23:27:35 -0400 Source: m2crypto Architecture: source Version: 0.36.0-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi <mo...@debian.org> Changed-By: Sandro Tosi <mo...@debian.org> Closes: 959947 964299 Changes: m2crypto (0.36.0-1) unstable; urgency=medium . * New upstream release * debian/control - add Breaks+Replaces: m2crypto-doc on -doc pkg; Closes: #959947, #964299 - wrap-and-sort - bump compat level to 13 * debian/patches/{d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch, d67b8e3d2682eb70248d7070d860dabe5a003d52.patch} - drop patches, merged upstream Checksums-Sha1: 273951e3fa4ca1bb53adb102598fe6070b4618d9 2319 m2crypto_0.36.0-1.dsc d35bb3322167b173c3aeb4854dc04ab969e495ae 447632 m2crypto_0.36.0.orig.tar.xz 417ab6425c02a96f1e724f1295fd574eae9b4ae6 58068 m2crypto_0.36.0-1.debian.tar.xz 2ae94320fc561e4e04979c10f8c491c9f92656c3 8032 m2crypto_0.36.0-1_source.buildinfo Checksums-Sha256: 7130af610dedb0d899bb192373e62309600bd0139dced687d15b88023289d536 2319 m2crypto_0.36.0-1.dsc f561a103742a5a8a99d9912f962921dea7a3529d2be66591401b4b7a95ae718f 447632 m2crypto_0.36.0.orig.tar.xz 075c9991254b7accb1c8b01a6835bd9516aa85b155b3ce29d6ce510b68c36eea 58068 m2crypto_0.36.0-1.debian.tar.xz 0d4238e30807e36172a20205465c6c78f8083eea798b027b2a914a3c1ca0da7d 8032 m2crypto_0.36.0-1_source.buildinfo Files: dbc90d6fef203a06c5edc8c301939c99 2319 python optional m2crypto_0.36.0-1.dsc 4c58d52993840e7656fcd35666e90f50 447632 python optional m2crypto_0.36.0.orig.tar.xz 9396f5ef506b5a6a3dee2ba9a4fc3b95 58068 python optional m2crypto_0.36.0-1.debian.tar.xz f08543c887660f1fff32c803fa578a6b 8032 python optional m2crypto_0.36.0-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8PyTkACgkQh588mTgB qU9/8w/+JXi8edTB/RL0RQVSGhZHzLYCXYt26d3ELQVfdFUiK4WpTgTzk6EzN/Vx hDoEQYMhWTtSlmTzq2jTgagiQIITfVesT46m3cXFGLRYgRe/WjODSdHyAG8h0Lu/ b2+9Ol81xLuUxaYVVcmoI8x6QA3m6iDSa8IH80WKivAka5PGx650gKTDyKJM4+3e k3onkM2+Y1Qw0fv0MGqKI5rH2UGPdnpb0d/37wn2Rgx0wUEixoqcWRiHiLq8/s0G IVX1BZwCONY0ZFLN30ujxTziPYJlHVUv15cWMCNlmjWxeV2HNCSwlyBZdL3rgKp/ wgn1AkTVTgEaCJ89LlPv78FCIXibj5Nm61YX5lQ+LZsxywY0+k9lE//0qfkWPZrp gJhKlWNZIH6SsN/v8iBleMMp9mugg6bw+yfV4qlBfLFJEXEpu4rl2iSWrQBfSGFr Vwl9yrjAfM+xVlwDAvcvDsarU7bmMLk9ffwrhf3Z6U2sW8pk/JEZpCJbmT9S3+vX s2EuOXnKDqf9ChEeHfE0WAYAiGuuIxiyVDxZr8NDTSCJEgbsnzuIhP9tISWssm8T lei9wHOgkLoX2eTKZ+E/PUsxGE2/RhSJL0PMd+7cTPZWDxVdorvJ3zjnUakSh5lT u5Sx2wwrEXzw5yLJKnfYWD4/lDKQj0HuhTsn8kYROI9O5xWahVo= =LJRc -----END PGP SIGNATURE-----
--- End Message ---
