Sean Whitton:
> Hello,
>
> On Fri 09 Nov 2018 at 09:46PM GMT, Niels Thykier wrote:
>
>> I suspect we are missing an exception allowing the binary targets to
>> write the produced binaries in the parent directory of the unpacked
>> source tree.
>> Otherwise pretty much all packages violate the p
Hello,
On Sat 03 Nov 2018 at 11:42PM +0100, Bill Allombert wrote:
>> How about:
>>
>> As an exception, required targets may write to the directory specified
>> by the ``TMPDIR`` environment variable (or ``/tmp`` if that is not
>> set), provided that files created in that directory are
Hello,
On Fri 09 Nov 2018 at 09:46PM GMT, Niels Thykier wrote:
> I suspect we are missing an exception allowing the binary targets to
> write the produced binaries in the parent directory of the unpacked
> source tree.
> Otherwise pretty much all packages violate the policy when they
> generate
Sean Whitton writes:
> On Fri 09 Nov 2018 at 05:39PM -0800, Russ Allbery wrote:
>> Thank you! Seconded.
> This change seems to be purely informative; could you say why you think
> it needs seconding, please?
Oh, sorry, I didn't even double-check whether there was normative
language, just made
Hello,
On Thu 08 Nov 2018 at 02:51PM GMT, Ian Jackson wrote:
> How about:
>
> Package builds MAY be affected, sometimes adversely, by the
> installation of additional packages beyond the Build-Depends
> and build-essential, subject to the following rules:
>
> Nature of package
Hello,
On Sun 04 Nov 2018 at 12:38AM +0100, Santiago Vila wrote:
> Maybe the relevant paragraph in policy is this one instead:
>
> If build-time dependencies are specified, it must be possible to build
> the package and produce working binaries on a system with only
> essential and build-es
Hello,
On Fri 09 Nov 2018 at 05:39PM -0800, Russ Allbery wrote:
> Thank you! Seconded.
This change seems to be purely informative; could you say why you think
it needs seconding, please?
--
Sean Whitton
signature.asc
Description: PGP signature
Hello Dmitry,
On Fri 09 Nov 2018 at 08:17AM GMT, Dmitry Bogatov wrote:
> Examples on which you can base your systemd integration on is available in
> the man page systemd.unit(8). An example on which you can base your
> -``/etc/init.d`` scripts is found in ``/etc/init.d/skeleton``.
> +``/etc/in
Your message dated Sat, 10 Nov 2018 16:56:07 -0700
with message-id <87k1lktrl4@iris.silentflame.com>
and subject line Re: Bug#850171: Recommend that manpages contain an EXAMPLES
section
has caused the Debian Bug report #850171,
regarding debian-policy: Patch so that there is an Example section
Processing commands for cont...@bugs.debian.org:
> tag 850171 +wontfix
Bug #850171 [debian-policy] debian-policy: Addition of having an 'EXAMPLES'
section in manual pages debian policy 12.1
Bug #850289 [debian-policy] debian-policy: Patch so that there is an Example
section in manual pages
Added
Your message dated Sat, 10 Nov 2018 16:56:07 -0700
with message-id <87k1lktrl4@iris.silentflame.com>
and subject line Re: Bug#850171: Recommend that manpages contain an EXAMPLES
section
has caused the Debian Bug report #850171,
regarding debian-policy: Addition of having an 'EXAMPLES' section
On Fri, Nov 09, 2018 at 08:17:42AM +, Dmitry Bogatov wrote:
> From e3457ee94e7293dbd59c9651d82d0c07fda50b33 Mon Sep 17 00:00:00 2001
> From: Dmitry Bogatov
> Date: Fri, 9 Nov 2018 08:02:01 +
> Subject: [PATCH] Update information about example init.d script
>
> According to #913154, there
On Thu, Nov 08, 2018 at 02:51:55PM +, Ian Jackson wrote:
> [...]
Looks ok at first read, maybe a little bit too much normative.
One minor comment:
> (i) a failure of the build, in which case the additional packages
> MUST be declared in Build-Conflicts);
As we talked before, that's
13 matches
Mail list logo
