On Wed, 25 Jul 2018 at 05:11:15 +0100, Ian Jackson wrote:
> ISTM that in days gone by this would have been (should have been) a
> wishlist item for invoke-rc.d. The interface was defined in
> invoke-rc.d(8) and README.policy-rc.d.gz.
...
> Nowadays, there is systemd too. I have no idea whether
>
On Wed, Jul 25, 2018 at 10:18:22AM +0100, Simon McVittie wrote:
> policyrcd-script-zg2 is an adapter between the invoke-rc.d-defined API
> (which says the policy-rc.d script must be in /usr/sbin) and what that
> API should maybe have been all along (additionally looking for the script
> in a config
Marc Haber writes ("Re: Bug#804018: options to avoid service startup on package
installation"):
> On Wed, Jul 25, 2018 at 10:18:22AM +0100, Simon McVittie wrote:
> > policyrcd-script-zg2 is an adapter between the invoke-rc.d-defined API
> > (which says the policy-rc.d script must be in /usr/sbin)
Package: debian-policy
Version: 4.1.5.0
Severity: normal
Hi,
Some tools, like git-buildpackage, can support merging an upstream's
version history into Debian packaging repositories. This enables more
rich usage of (D)VCS when packaging - for example `git blame' works
properly.
Currently there's
control: tag -1 -patch
Hello,
On Mon 23 Jul 2018 at 08:09AM -0700, Jonathan Nieder wrote:
> It comes down to what "might not work" means.
>
> For example, "might reformat your hard drive" is an example of "might not
> work".
>
> This might seem pedantic, but it really isn't: I've seen packagers
Processing control commands:
> tag -1 -patch
Bug #685746 [debian-policy] debian-policy Consider clarifying the use of
recommends
Removed tag(s) patch.
--
685746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hello gregor,
On Mon 23 Jul 2018 at 01:40PM +0200, gregor herrmann wrote:
> Let me see if I got this right, and apply it to the typical pkg-perl
> package:
>
> CPAN distributions usually contain no NEWS file, and do contain a
> Changes/ChangeLog/... file which is "an upstream release notes file"
Hello Bill,
On Mon 23 Jul 2018 at 12:29PM +0200, Bill Allombert wrote:
> The issue is that the recommendation does not include a rationale, and
> it seems to me the rationale is based on an implicit definition of
> changelog which is not communicated either (or more precisely, it is
> based on th
Processing control commands:
> tag -1 -patch +pending
Bug #813471 [debian-policy] Permit some network access to the build host
Removed tag(s) patch.
Bug #813471 [debian-policy] Permit some network access to the build host
Added tag(s) pending.
--
813471: https://bugs.debian.org/cgi-bin/bugreport
control: tag -1 -patch +pending
Hello Paul, Ian,
It looks like we have a clear consensus that my patch is fine, but while
it might be that there is further loosening of the restriction on
network access that should be done in addition to my patch, we do not
know exactly what yet.
So I'm applying
Processing control commands:
> tag -1 +moreinfo
Bug #904608 [debian-policy] Support specifying upstream VCS location in
debian/control
Added tag(s) moreinfo.
--
904608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
control: tag -1 +moreinfo
Hello Iain,
On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote:
> Some tools, like git-buildpackage, can support merging an upstream's
> version history into Debian packaging repositories. This enables more
> rich usage of (D)VCS when packaging - for example `git blam
Hi,
Sean Whitton wrote:
> On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote:
>> Some tools, like git-buildpackage, can support merging an upstream's
>> version history into Debian packaging repositories. This enables more
>> rich usage of (D)VCS when packaging - for example `git blame' works
>
Hi,
Sean Whitton wrote:
> On Mon 23 Jul 2018 at 01:40PM +0200, gregor herrmann wrote:
>> Let me see if I got this right, and apply it to the typical pkg-perl
>> package:
>>
>> CPAN distributions usually contain no NEWS file, and do contain a
>> Changes/ChangeLog/... file which is "an upstream rel
Hello,
On Wed 25 Jul 2018 at 07:01PM -0700, Jonathan Nieder wrote:
> I share gregor's discomfort: I don't think we've thought this through.
I too want Policy to be as correct as possible, but this bug has been
open for ten years and one thing upon which there is certainly consensus
is that the c
Sean Whitton wrote:
> On Wed 25 Jul 2018 at 07:01PM -0700, Jonathan Nieder wrote:
>> I share gregor's discomfort: I don't think we've thought this through.
>
> I too want Policy to be as correct as possible, but this bug has been
> open for ten years and one thing upon which there is certainly con
Hi,
Sean Whitton wrote:
> Thank you for the discussion, Ian and Simon. Here is the beginnings of
> a patch:
>
>> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
>> index 9e7d79c..f27226e 100644
>> --- a/policy/ch-source.rst
>> +++ b/policy/ch-source.rst
>> @@ -40,9 +40,15 @@ example, if
[if you were CCed on this e-mail: this was because you seconded a
previous version of the patch which included a recommendation which I
have now dropped, and I hope you'll second the revised patch, further
down this e-mail]
Hello Jonathan,
On Wed 25 Jul 2018 at 08:57PM -0700, Jonathan Nieder wrot
On Thu, Jul 26, 2018 at 01:05:16PM +0800, Sean Whitton wrote:
> diff --git a/policy/ch-docs.rst b/policy/ch-docs.rst
> index 1de221f..e990f34 100644
> --- a/policy/ch-docs.rst
> +++ b/policy/ch-docs.rst
> @@ -255,32 +255,45 @@ files may be installed into ``/usr/share/doc/package``.
>
> .. _s-cha
Hello,
On Wed 25 Jul 2018 at 06:20PM -0700, Jonathan Nieder wrote:
> I would have expected to find this information in debian/copyright. The
> Source field there sometimes names an upstream VCS but isn't required to
> do so; I'd be in favor of some tightening of the requirements in
> copyright-f
20 matches
Mail list logo
