On Fri, May 17, 2019 at 10:00:17PM +0200, Paul Gevers wrote:
> 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.
> >
> >
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 not
Hi Santiago,
On 16-05-2019 20:24, Santiago Vila wrote:
> On Thu, May 16, 2019 at 07:43:09PM +0200, Paul Gevers wrote:
>
>> The reason why it got removed, is that nobody was looking after razor.
>> Otherwise, preventing removal would have been easy.
>
> Indeed. If I had known that it was going to
On Thu, May 16, 2019 at 07:43:09PM +0200, Paul Gevers wrote:
> The reason why it got removed, is that nobody was looking after razor.
> Otherwise, preventing removal would have been easy.
Indeed. If I had known that it was going to be removed, I would have
downgraded the severity of the bug befor
Control: tags -1 moreinfo
Hi Santiago,
On 16-05-2019 17:52, Santiago Vila wrote:
> Please allow razor back in testing, as a freeze exception.
razor was already on my radar, and I already have considered an exception.
> It was autoremoved because there was a RC bug in the BTS, but the
> real pro
Package: release.debian.org
User: release.debian@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 serv
6 matches
Mail list logo
