Package: debian-policy
Version: 4.1.1.1
In the section on log files[1], the example uses start-stop-daemon:
postrotate
start-stop-daemon -K -p /var/run/foo.pid -s HUP -x /usr/sbin/foo -q
endscript
while elsewhere in the policy manual it is suggested to use invoke-rc.d
Inspecting my own syst
Package: debian-policy
Author and copyright holder are not always the same person/entity.
E.g. the work may be authored by Bob but the copyright is assigned to
his employer Acme, Inc, e.g.
License: GPL2
Copyright: 2014, Acme, Inc http://acme.example.org
Author: Bob, http://example.org/bob
For c
On 03/02/14 20:17, Jonathan Nieder wrote:
> severity 737559 wishlist
> user debian-pol...@packages.debian.org
> usertags 737559 = normative issue
> quit
>
> Hi Daniel,
>
> Daniel Pocock wrote:
>
>> Author and copyright holder are not always the same person
On 03/02/14 20:36, Jonathan Nieder wrote:
> Daniel Pocock wrote:
>
>> Just to clarify, I do not believe that maintaining this field should be
>> obligatory
>>
>> It should be an optional field
>>
>> Defining it formally in the standard and havin
On 03/02/14 20:55, Jonathan Nieder wrote:
> Daniel Pocock wrote:
>
>> I've only come across one package which included public-domain material
>> so far. In this case, I put a note about the author in the comments.
>
> Yep - that works, too.
>
> [...]
&
On 03/02/14 21:58, Russ Allbery wrote:
> Daniel Pocock writes:
>
>> There are cases where I would have used it and I believe that
>> recognising people's work (even if they have assigned their rights) is
>> an important way of showing our thanks and acknowledgment
Package: debian-policy
Severity: important
Some of this has been discussed in other bugs such as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60979
requesting an init script action for restart-only-if-running
Consider the following:
- package foo provides a daemon
- package foo-plugin-bar p
Package: debian-policy
Severity: important
If postinst or one of the other scripts does a service restart and the
restart operation fails, should the postinst abort or should it mask the
error, continue and return success?
If it continues, is there any other convention for reporting the
problem,
On 22/10/15 12:26, Henrique de Moraes Holschuh wrote:
> On Tue, Oct 20, 2015, at 14:08, Daniel Pocock wrote:
>> If postinst or one of the other scripts does a service restart and the
>> restart operation fails, should the postinst abort or should it mask the
>> error, contin
9 matches
Mail list logo
