Your message dated Tue, 25 Feb 2020 08:52:56 +0100 with message-id <20200225075256.gv6...@an3as.eu> and subject line Closing bug since python-cobra 0.14.2-2 MIGRATED to testing has caused the Debian Bug report #951690, regarding src:python-cobra: fails to migrate to testing for too long 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.) -- 951690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: python-cobra Version: 0.14.1-1 Severity: serious Control: fixed -1 0.14.2-2 Tags: sid bullseye User: release.debian....@packages.debian.org Usertags: out-of-sync 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:python-cobra in its current version in unstable has been trying to migrate for 354 days. 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 marked the version in unstable as fixing this bug, 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
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Hi, I'm hereby closing this bug since the package has just migrated to testing. Kind regards Andreas. ----- Forwarded message from Debian testing watch <nore...@release.debian.org> ----- Date: Tue, 25 Feb 2020 04:39:22 +0000 From: Debian testing watch <nore...@release.debian.org> To: python-co...@packages.debian.org Subject: python-cobra 0.14.2-2 MIGRATED to testing FYI: The status of the python-cobra source package in Debian's testing distribution has changed. Previous version: 0.14.1-1 Current version: 0.14.2-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. _______________________________________________ Debian-med-packaging mailing list debian-med-packag...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging ----- End forwarded message ----- -- http://fam-tille.de
--- End Message ---
