Daniel, et al.
I was preparing a fix for this by copying some support scripts from
other exporters when I noticed a couple of things, and wanted to check
with you before making any change.
This exporter is running with user postfix, while all the others use the
prometheus user. I understand
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
>> as is and ask the release
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
> as is and ask the release team to mark it buster-ignore.
>
Could you kindly point me to where the process is described for this? I’m
not sure what I’d need to do
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 FTP Team's job
On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman
wrote:
> It's not the FTP Team's job to fix policy compliance issues in packages.
> If you have a problem with that being a policy must, then you should take
> it up with the policy team.
>
Yeah, I’ll post to #911165
>
> I completely understand
It's not the FTP Team's job to fix policy compliance issues in packages. If
you have a problem with that being a policy must, then you should take it up
with the policy team.
I completely understand the frustration, but in my own packages I take the time
to do it because Debian policy says
Can you provide a patch if you care about sysvinit please? The Go packaging
team is pretty manpower-constrained and non-systemd is a niche case, so 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
>