Your message dated Fri, 17 May 2019 22:00:17 +0200 with message-id <c16a864c-208d-75aa-2b0e-3ef154d67a42@debian.org> and subject line Re: Bug#929082: unblock: razor/1:2.85-4.2 has caused the Debian Bug report #929082, regarding unblock: razor/1:2.85-4.2 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 owner@bugs.debian.org immediately.) -- 929082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929082 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian BTS <submit@bugs.debian.org>
- Subject: unblock: razor/1:2.85-4.2
- From: Santiago Vila <sanvila@unex.es>
- Date: Thu, 16 May 2019 17:52:49 +0200 (CEST)
- Message-id: <[🔎] alpine.DEB.2.20.1905161719370.26941@tulipan.isla-invisible.es>
Package: release.debian.org User: release.debian.org@packages.debian.org Usertags: unblock Severity: normal Please allow razor back in testing, as a freeze exception. It was autoremoved because there was a RC bug in the BTS, but the real problem was not in the package itself but in the razor servers by cloudmark (for which the razor package acts as a client). The problem is already solved. Details about this in Bug #924583. I'm filing this only as a DD and long-time user of razor because the package is currently orphaned (#866833). IMO dropping razor from buster does not really help our users. (No debdiff to attach because the problem was solved in the razor servers, not in the razor package). Thanks.
--- End Message ---
--- Begin Message ---
- To: 929082-done@bugs.debian.org
- Cc: Santiago Vila <sanvila@unex.es>, Holger Levsen <holger@layer-acht.org>
- Subject: Re: Bug#929082: unblock: razor/1:2.85-4.2
- From: Paul Gevers <elbrus@debian.org>
- Date: Fri, 17 May 2019 22:00:17 +0200
- Message-id: <c16a864c-208d-75aa-2b0e-3ef154d67a42@debian.org>
- In-reply-to: <[🔎] 20190516200308.5txd3ccbfpwsqps5@layer-acht.org>
- References: <[🔎] alpine.DEB.2.20.1905161719370.26941@tulipan.isla-invisible.es> <[🔎] fa078b01-423e-fe4e-10cf-3bcdfe0f84eb@debian.org> <[🔎] 20190516182448.2gyf54qf2ctvy62l@nucold> <[🔎] alpine.DEB.2.20.1905161719370.26941@tulipan.isla-invisible.es> <[🔎] b33e1893-bc97-c462-abe2-d1209fc4267a@debian.org> <[🔎] 20190516200308.5txd3ccbfpwsqps5@layer-acht.org>
Hi, On 16-05-2019 22:03, Holger Levsen wrote: > On Thu, May 16, 2019 at 09:52:45PM +0200, Paul Gevers wrote: >> Well, if they are maintained by the QA group, there are at least around >> 90 people notified of stuff. > > no. noone is notified about bugs in packages maintained by the QA group. > (or maybe some poor soul is, but noone is reading those notices *if* > someone receives them.) I have just added an unblock hint. Santiago, could I kindly ask you to at least monitor the package (e.g. via tracker.d.o) until a new maintainer steps up? Don't hesitate to upload a version with the maintainer set to the QA group *after* the release of buster, despite of the fact that Holger confirmed my fears. PaulAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---