My recollection is that you mail debian-release and ask.
Scott y
On February 7, 2019 7:51:29 AM UTC, Michael Stapelberg
wrote:
>On Thu, Feb 7, 2019 at 8:46 AM Scott Kitterman
>wrote:
>
>> No. It's an actual policy violation, so the bug is correct. I'd
>leave it
>> a
No. It's an actual policy violation, so the bug is correct. I'd leave it as
is and ask the release team to mark it buster-ignore.
Scott K
On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg
wrote:
>On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman
>wrote:
>
>> It's not the
gt;any
>help is appreciated. Thanks!
>
>On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman
>wrote:
>
>> Package: prometheus-postfix-exporter
>> Version: 0.1.2-1
>> Severity: serious
>> Justification: Policy 9.11
>>
>> Excerpt from policy 9.11:
>>
Package: prometheus-postfix-exporter
Version: 0.1.2-1
Severity: serious
Justification: Policy 9.11
Excerpt from policy 9.11:
However, any package integrating with other init systems
must also be backwards-compatible with sysvinit by providing a SysV-
style init script with the same name as and
otential to
> DoS the services that they connect to or hosts they run on, if they are
> scraped frequently enough.
>
> On 02.02.19 08:28, Scott Kitterman wrote:
> > I am concerned that an external package using showq is going to be
> > problematic. Some excerpts from showq (8):
I am concerned that an external package using showq is going to be
problematic. Some excerpts from showq (8):
The showq(8) daemon reports the Postfix mail queue status. The output is
meant to be formatted by the postqueue(1) command, as it emulates the Sendmail
`mailq' command.
SECURITY
Package: cloudsql-proxy
Version: 1.13-1
Severity: important
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
