Control: severity -1 serious Hi,
On Sun, Jun 09, 2019 at 01:44:18PM +0200, Salvatore Bonaccorso wrote: > On Sun, Jun 09, 2019 at 01:14:57PM +0300, Sergey B Kirpichev wrote: > > On Sun, Jun 09, 2019 at 12:08:21PM +0200, Salvatore Bonaccorso wrote: > > > After some time passed, on 2019-06-03, another Debian security team > > > member (Moritz Muehlenhoff <j...@debian.org>) raised the severity to a > > > release critical value. > > > > For no reasons. > > I gave a reason though now in my previous mail, right in the sentence > following after that. > > > > Could you please work out with the Release team via an unblock request > > > if they would wave through the version or a sheduled a targeted fix > > > via testing-proposed-updates? > > > > Yes, I'm planing backports for these fixes. I don't know why this > > require increase in the bug severity. > > Perfect, thanks! The increase in severity was done as per above, to > make sure it is marked release critical and not missed for the > release of buster. As the security team considers this an issue that needs to be fixed for buster, I'm increasing the severity. Please do not downgrade it again. Note that the revert Paul mentioned in #930313 will need to be in unstable before 2019-06-25 13:00 UTC. Otherwise we'll be forced to remove monit from buster manually. See the announcement of the release timeline: https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html Thanks, Ivo
