[pkg-go] Bug#921351: Bug#921351: prometheus-postfix-exporter: Init script missing

[Scott Kitterman]

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 it's required, not because I particularly care about sysvinit.

Scott K

On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <stapelberg at debian.org> wrote:
>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 <debian at kitterman.com>
>wrote:
>
>> 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 equivalent functionality
>> to any init-specific job, as this is the only start-up configuration
>> method guaranteed to be supported by all init implementations.
>>
>> The package violates a policy must by not providing s sysvint init
>script.
>>
>> Scott K
>>
>> _______________________________________________
>> Pkg-go-maintainers mailing list
>> Pkg-go-maintainers at alioth-lists.debian.net
>>
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers